I'm using BOINC Beta version 3.19 M1 Release on a Dell 8200 desktop PC under WinXP.

I can't seem to get any work units from the server. For a while there, I was chugging along, but now my message log is full of sequences like this:

--- - 2004-06-25 22:05:59 - Fewer active results than CPUs; requesting more work
SETI@home - 2004-06-25 22:05:59 - Requesting 85908 seconds of work
SETI@home - 2004-06-25 22:05:59 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-25 22:06:04 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-25 22:06:04 - Message from server: Not sending work - last RPC too recent: 225 sec

Should I be concerned? Did you guys really run out of work? :)

Read the main page: http://setiboinc.ssl.berkeley.edu/sah/
Right column

yes, we have a WU shortage.


----------------------
Jordâ„¢
[url=http://www.boinc.dk/index.php?page=user_statistics&userid=41965]

OK, sorry!

I scanned the main page, but nothing really jumped out at me. I'm afraid that front page is one vast sea of homogenous typography. When you have a *major* glitch like this, maybe you could use some color or bold fonts to draw attention to the current status?

Also, in the HelpDesk areas, it defaults to "Most Asked Questions", so my question (and everybody else's, apparently), does not show up. When I switched to "Most Recent Questions", it was pretty clear that I was not alone.

RPC too recent means that your computer has tried to contact the server more recently than it is allowed to. The backoff time that the server enforces is I believe 10 minutes. This is to ensure that a computer that has a problem that crashes after a few seconds does not get several thousand WUs over the course of a day. This scenario has happened in testing.

If you are interested in programmereese, RPC stands for Remote Proceedure Call.