I just did 3 small WU's this morning but I am empty now and have had no work available since 16:51 Eastern. What I do then is try to update manually a few times and if that doesn't retrieve any WU's I just let it be. I did have Predictor@Home sharing 50/50 with SETI@Home but that is down now too. Some say to run the old classic SETI when this happens, leave BOINC up and see if it tries to get more WU's but you may have to manually update to check for more work if BOINC runs at a lower priority.
As long as you have contacted the server as shown in the logs like such:
SETI@home - 2004-07-24 17:17:04 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-24 17:17:08 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-07-24 17:17:08 - Message from server: No work available
SETI@home - 2004-07-24 17:17:08 - No work from project
SETI@home - 2004-07-24 17:17:08 - Deferring communication with project for 1 hours, 0 minutes, and 0 seconds
--- - 2004-07-24 17:23:20 - Fewer active results than CPUs; requesting more work
SETI@home - 2004-07-24 17:23:20 - Requesting 78704 seconds of work
SETI@home - 2004-07-24 17:23:20 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-24 17:23:23 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-07-24 17:23:23 - Message from server: No work available
you did all you can. Like I said earlier they have a few growing pains. Also they only crunch each WU 3 times as compared to many, many times for the classis S@H, so each WU you do get will be of more importance but they'll run out quicker or so they say. You could try varying the cache size to see if that changes things.
That's the kind of data my status screen shows. Good to know. Thanks for the info.
I tried to install the regular 3.08 and had some issue, so figured what the heck and do BOINC. I'll try again on that machine.