This has happened in several of my host. Maybe it has already been corrected for v4.46, but I dont remember seen it mentioned.

This host v4.45 is attached to (project, share, ltd):

SETI 20% 177.242
CPDN 20% -183.358
Predictor 60% 6.115

6/24/2005 8:49:37 AM||Resuming network activity
6/24/2005 8:49:37 AM|SETI@home|Started upload of 31ja04aa.10505.5282.498562.49_2_0
6/24/2005 8:49:37 AM|SETI@home|Started upload of 29fe04aa.10628.31040.678406.153_0_0
6/24/2005 8:49:38 AM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
6/24/2005 8:49:38 AM|climateprediction.net|Requesting 0 seconds of work, returning 0 results
6/24/2005 8:49:40 AM|SETI@home|Finished upload of 31ja04aa.10505.5282.498562.49_2_0
6/24/2005 8:49:40 AM|SETI@home|Throughput 242922 bytes/sec
6/24/2005 8:49:41 AM|SETI@home|Finished upload of 29fe04aa.10628.31040.678406.153_0_0
6/24/2005 8:49:41 AM|SETI@home|Throughput 42964 bytes/sec
6/24/2005 8:50:40 AM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
6/24/2005 8:50:44 AM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
6/24/2005 8:50:44 AM|ProteinPredictorAtHome|Requesting 0 seconds of work, returning 0 results
6/24/2005 8:50:46 AM|ProteinPredictorAtHome|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
6/24/2005 8:51:22 AM||request_reschedule_cpus: project op
6/24/2005 8:51:23 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/24/2005 8:51:23 AM|SETI@home|Requesting 0 seconds of work, returning 2 results
6/24/2005 8:51:25 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
6/24/2005 8:51:29 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/24/2005 8:51:29 AM|SETI@home|Requesting 86400 seconds of work, returning 0 results
6/24/2005 8:51:31 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
6/24/2005 8:51:31 AM|SETI@home|Message from server: Not sending work - last RPC too recent: 6 sec
6/24/2005 8:51:31 AM|SETI@home|No work from project
6/24/2005 8:51:32 AM|SETI@home|Deferring communication with project for 10 minutes and 4 seconds


Both CPDN and Predictor were set to "not request new work". There were 2 Seti wu ready to upload and it was working on one CPDN unit.

After network activity was resumed, it uploaded the seti wu, contacted CPDN and predictor, then contacted Seti, but did not ask for new work and then 4 seconds later it contacted again Seti asking for work. What changed in this 4 seconds?

This is not a great problem in this host which is almost always conected, but on other host of mine where I use a modem this is quite a problem.

Any idea?

---

This has been seen by many (myself included). It's almost like there are two different parts of the program requesting access to the scheduler and the left hand doesn't know what the right hand is doing. One contacts the scheduler for it's purpose then seconds later (after the scheduler recalculates it's needs) the other requests work and hits the 10 minute wall, and you get the "Last RPC too recent" message.

tony

It may have to do with the new setup of the scheduler, where when it sends in units, it immediately there-after sends the 'report' signal to the server as well. That's two times that the scheduler is needed.

---