last RPC to recent.

Message boards : Number crunching : last RPC to recent.
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile adrianxw
Avatar

Send message
Joined: 14 Jul 99
Posts: 173
Credit: 1,698,756
RAC: 3
Denmark
Message 112757 - Posted: 19 May 2005, 8:55:39 UTC

I have no S@H wu's at the moment. On eof my CPU's finished it's unit, then crunched one of those really short units. When it asked for more work it said...

19/05/2005 10:42:16|SETI@home|Starting result 31dc04aa.14083.23698.367328.50_3 using setiathome version 4.09
19/05/2005 10:42:17|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
19/05/2005 10:42:18|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
19/05/2005 10:43:02||May run out of work in 0.10 days; requesting more
19/05/2005 10:43:02|SETI@home|Requesting 58.33 seconds of work
19/05/2005 10:43:02|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
19/05/2005 10:43:03|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
19/05/2005 10:43:03|SETI@home|Message from server: Not sending work - last RPC too recent: 45 sec

... too recent? If I was not running other projects, my system would be idle now. Something not right here?
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
ID: 112757 · Report as offensive
Profile MikeSW17
Volunteer tester

Send message
Joined: 3 Apr 99
Posts: 1603
Credit: 2,700,523
RAC: 0
United Kingdom
Message 112758 - Posted: 19 May 2005, 9:25:01 UTC - in response to Message 112757.  

I have no S@H wu's at the moment. On eof my CPU's finished it's unit, then crunched one of those really short units. When it asked for more work it said...

19/05/2005 10:42:16|SETI@home|Starting result 31dc04aa.14083.23698.367328.50_3 using setiathome version 4.09
19/05/2005 10:42:17|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
19/05/2005 10:42:18|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
19/05/2005 10:43:02||May run out of work in 0.10 days; requesting more
19/05/2005 10:43:02|SETI@home|Requesting 58.33 seconds of work
19/05/2005 10:43:02|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
19/05/2005 10:43:03|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
19/05/2005 10:43:03|SETI@home|Message from server: Not sending work - last RPC too recent: 45 sec

... too recent? If I was not running other projects, my system would be idle now. Something not right here?


At 10:42:18 it sent one request, at 10:43:02 it sent another.

IMO a bug.

Workaround is to have a larger cache, 1 to 3 days is fine for a single project user.


ID: 112758 · Report as offensive
Astro
Volunteer tester
Avatar

Send message
Joined: 16 Apr 02
Posts: 8026
Credit: 600,015
RAC: 0
Message 112766 - Posted: 19 May 2005, 9:39:13 UTC

I too have seen the "RPC too recent" message. It used to mean you were pushing the "project update" to often, but now it's different. It seems to create this message on it's own. like a request from one part of boinc isn't known by another part of boinc and creating that message. I think it's a small bug. it does eventually get the needed work though.

tony
ID: 112766 · Report as offensive

Message boards : Number crunching : last RPC to recent.


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.