August 30, 2005
We're back online: We have been offline from Tuesday, August 23 until this afternoon. We haven't solved all our server problems - turning the whole project back on will allow us to get more dignostics (and observe the system under stress). And, of course, it's always better when clients can connect to our servers. Please note that the servers may be going up/down over the next few days as we still work some things out. Also note that SETI@home classic is temporarily turned off to conserve bandwidth as all BOINC clients are attempting to reconnect.

As ever, read the front page for news before you post on the forums. And please leave your bad language at home.

---

Hi !
I get the following message from BOINC (many times):
14-01-2000 01:30:01|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
14-01-2000 01:30:01|SETI@home|Requesting 8640 seconds of work, returning 0 results
14-01-2000 01:30:22|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
14-01-2000 01:30:22|SETI@home|No schedulers responded
14-01-2000 01:30:23|SETI@home|Deferring communication with project for 2 minutes and 24 seconds

or this one:
14-01-2000 01:19:50||request_reschedule_cpus: project op
14-01-2000 01:19:51|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
14-01-2000 01:19:51|SETI@home|Requesting 8640 seconds of work, returning 0 results
14-01-2000 01:19:58|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
14-01-2000 01:19:58|SETI@home|Message from server: Not sending work - last RPC too recent: 313 sec


whats the problem ? what should I do ? ... and why the f... is this BOINC crap a good idea ?

---