Why am I getting the "no work avalible" message?

I still haven't solved my checksum problem mentioned in my other post. I tried again to see if it would work, and now I am getting 'no work avalible'. How is this possible? Have we run out of data already? How could we run out of data when most of the SETI people are still running classic? If "finite work supply" means this, I'm afraid that every radio dish in the world wouldn't be able to keep up! Astropulse isn't going to make a difference either. Please, someone tell me this is just a serever problem, or else SETI@home will be destroyed in a few days! The server will be overwhelmed with requests, people trying over and over and over to get a WU when it gets made. And then only three of the millons of people will be off the server for a day. So, is this what will happen or is the server still down? I knew it was down an hour ago but then it didn't give me the 'no work avalible' message.

Well, that worked sort of. I got some work, but only about a days worth. I have it set for 2-4 days, so it tried to get some more. I got the same message. Here is the lines above it:


--- - 2004-06-24 16:47:32 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-24 16:47:32 - Requesting 123475 seconds of work
SETI@home - 2004-06-24 16:47:32 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-24 16:47:36 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-24 16:47:36 - Message from server: No work available



I hope I can get more work before my current stuff runs out. Why is this happening already? Did the matinence stop for 10 miniutes when I downloaded my units, and then start again?

Hmmm, it turns out I only have enough work left to last a few hours, and I still can't get new stuff. Please help! I want to get new WU's before I run out.

> The lines above the no work availble message give an indication of why no work
> is available. The project was down for maintenance for a while this
> afternoon, and you may have tried to connect during the outage.
> jm7

Um, you mean it's been down since 8am CST... and is still down.

And on my home computer it does not mention anything about the Project being down.

--- - 2004-06-24 18:16:39 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-24 18:16:39 - Requesting 339291 seconds of work
SETI@home - 2004-06-24 18:16:39 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-24 18:16:44 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-24 18:16:44 - Message from server: No work available
SETI@home - 2004-06-24 18:16:44 - No work from project
SETI@home - 2004-06-24 18:16:44 - Deferring communication with project for 4 minutes and 56 seconds
--- - 2004-06-24 18:21:41 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-24 18:21:41 - Requesting 339477 seconds of work
SETI@home - 2004-06-24 18:21:41 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-24 18:21:45 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-24 18:21:45 - Message from server: Not sending work - last RPC too recent: 302 sec
SETI@home - 2004-06-24 18:21:45 - No work from project
SETI@home - 2004-06-24 18:21:45 - Deferring communication with project for 15 minutes and 17 seconds

And it's been doing this at my work computer for 11 hours now.
:(

The server is being overwhelmed with requests from everyone. Have some patience and read up on the main site of this Project. ;)

June 24, 2004
To handle increased demand for more workunits, we are bringing another splitter online as quickly as possible. We are also working on increasing overall system performance. The overall system is experiencing twice the maximum load beta generated and is climbing. We are working to resolve the issues as quickly as possible.


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