Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 714 times and has 1 reply Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
sad Last RPC too Recent?

I'm running BOINC in windows because I have an X2 and want to use both processors, and right now BOINC is only running one work unit and when I tell it to update and get another I get:

11/28/2005 9:53:54 AM|World Community Grid|Message from server: Not sending work - last RPC too recent: 150 sec

I'm sure it's not that big of a deal but I hate to see one core go to waist hehe
[Nov 28, 2005 5:59:15 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Ingleside
Veteran Cruncher
Norway
Joined: Nov 19, 2005
Post Count: 974
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Last RPC too Recent?

To guard against computers spamming the server with requests, there is a delay between how often you can connect the scheduling-server.

This delay is configurable by BOINC-project, and WGC uses same delay as SETI@Home, 10 minutes.


The scheduling-server is always including this delay in all replys, so will not on it's own re-try too early. Only if manually hits "update" can you ask again too recent.


If you looks under the Project-tab, you'll normally see the delay counting-down "Communication deferred nn:nn:nn", so just wait till it counts-down to zero, and the client should automatically ask for more work. :)
----------------------------------------


"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
[Nov 29, 2005 12:02:56 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread