Insufficient work; requesting more

From Unofficial BOINC Wiki

Contents 1 General 2 Example Log(s) 2.1 Success 2.2 Failure 3 Other Related Messages

[edit] General

Message Type: Error Message

This message means that the BOINC Client Software's Work Buffer does not have enough work based on the Participant's Preferences.

This message is commonly received when the Participant first "Attaches" the BOINC Client Software to a specific Project.

[edit] Example Log(s)

[edit] Success

6/4/2005 6:32:55 PM|                             |Insufficient work; requesting more
6/4/2005 6:32:55 PM|http://predictor.scripps.edu/|Requesting 432000.00 seconds of work
6/4/2005 6:32:55 PM|http://predictor.scripps.edu/|Sending request to scheduler:
                                                  http://predictor.scripps.edu/predictor_cgi/cgi
6/4/2005 6:32:56 PM|http://predictor.scripps.edu/|Scheduler RPC to
                                                  http://predictor.scripps.edu/predictor_cgi/cgi
                                                  succeeded

Line-By-Line Explanation

• Insufficient work; requesting more

This message tells you that the BOINC Client Software wants to get more work for your Work Buffer, in this case we don't have an exact size for the Work Buffer.

• Requesting "x" seconds of work

This is just a message telling you how much work you need to get to satisfy the size you have selected for your Work Buffer. This number is always expressed in seconds.

• Sending request to scheduler: '(url)'

This message indicates that the BOINC Client Software is making the attempt to connect to the Project's Scheduling Server.

• Scheduler RPC to '(url)' succeeded

This message tells you that the communication session completed without error.

[edit] Failure

6/4/2005 6:32:16 PM|         |May run out of work in 2.50 days; requesting more
6/4/2005 6:32:16 PM|SETI@home|Requesting 4150.38 seconds of work
6/4/2005 6:32:16 PM|SETI@home|Sending request to scheduler:
                              http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/4/2005 6:32:37 PM|SETI@home|Scheduler RPC to      
                              http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/4/2005 6:32:37 PM|SETI@home|No schedulers responded
-+-+/\/\/\/\/\ Log Break /\/\/\/\/\-+-+-
6/4/2005 6:32:39 PM|SETI@home|Deferring communication with project for 57 seconds

Line-By-Line Explanation

• May run out of work in "x.y" days; requesting more

This message tells you that the BOINC Client Software wants to get more work for your Work Buffer, in this case it is set to two and a half days (2.5) days.

• Requesting "x" seconds of work

This is just a message telling you how much work you need to get to satisfy the size you have selected for your Work Buffer. This number is always expressed in seconds.

• Sending request to scheduler: '(url)'

This message indicates that the BOINC Client Software is making the attempt to connect to the Project's Scheduling Server.

• Scheduler RPC to '(url)' failed

This message tells you that the communication session did not complete without error.

• No schedulers responded

This message tells you the reason that the communication session did not succeed. In this case, there was no response from the Project's Scheduling Server. This is common when the project is Off-Line or the Server is busy servicing other requests.

• Deferring communication with project for "x" hours, "y" minutes, and "z" seconds

Because of the communications failure, we will use Exponential Back-Off to prevent our Host from "flooding" the Server with communication requests. I mean, if it is busy, maybe we should give it a break.

[edit] Other Related Messages

• Finished download of '(file)'
• Started download of '(file)'