Martin 53N 1W wrote:

QoJ wrote:

f/fgeorge wrote:

On Mon, 14 Mar 2005 20:48:19 -0500, "QoJ" <justabitch@dodgeit.com>
wrote:

SETI@home - 2005-03-14 20:46:20 - Requesting 4416 seconds of work
SETI@home - 2005-03-14 20:46:20 - Sending request to scheduler:
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-03-14 20:46:23 - Scheduler RPC to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2005-03-14 20:46:23 - Message from server: Not sending
work - last RPC too recent: 35 sec
SETI@home - 2005-03-14 20:46:23 - No work from project
SETI@home - 2005-03-14 20:46:23 - Deferring communication with
project for 10 minutes and 0 seconds

Seems like you and 80 thousand other people are all trying to get in
at the same time!
"Last RPC too recent" means you are trying too often and they system
is not going to let you in again for a little bit.

Well I like to click retry<G> thanks for explaining that RPC thingy!

The system is designed to 'back off' and wait for longer and longer
periods if the client continues to fail to get through to the servers.

This is a good idea. The wait periods are increased for everyone until
the server finally can successfully serve all the (now staggered)
requests. This avoids the server getting choked and dragged down to
just refusing an impossible flood of requests.

giggle sounds like group sex :)

The 'RPC' is the client calling to the server. Looks like you're too
clicky at more than two clicks a minute.

LOL that often?  I had no idea ;)

A little patience is a good thing (:-))

Yep it finally woke up and started crunching.....half way done now<G>

Happy crunchin',
Martin

Thanks Martin!