No work from project

From Unofficial BOINC Wiki

[edit] General

This message is an indication that the last connection by the BOINC Daemon to the Project resulted in no additional work for the Participant's Computer. There are a number of reasons that this might occur, the first and foremost of course is that the Project has not made up any new Work Units or Results.

It is also possible that the available work has been distributed to a specific class of computer and therefore there is no work that can be issued to the participant's computer as it is not of the required type.

So, there are a number of possibilities:

The Project has issued all work and has none on the Data Server to issue.
There are currently no Work Units that your system can process due to:
- Your computer thinks the prospective Work Unit is not worth the time and trouble.
- Insufficient CPU speed, your system cannot process any of the available Work Units before their deadlines.
- Insufficient disk space, your system cannot process any of the available Work Units because you do not have enough free space on your disk Drive.

Note: You might have set your allocation of disk space in your Preferences to a value that is too low. Increasing this limit may allow you to get more work for that project. Check with the Project's Web Site to see what is their recommended allocation.

The Project is over and there is no more work for that Project.
The Project is using Homogeneous Redundancy, which means that the Project wants all of the Results to come from "like" computers. This increases the reliability and accuracy of the Results.

This is not necessarily an "error" in the strictest sense, but a communication that is telling you that for one reason or another there is just nothing available for your systems to do. With the BOINC System allowing you to donate to several Projects your chances of running out of things to do is pretty remote. If you have at least two Projects selected and there is not work for the first Project it is very likely that the second Project will keep your computers happily munching away.

[edit] Example Log(s)

[edit] Scheduler Request Succeeded - Daily Quota Error

2005-06-03 11:02:39 [climateprediction.net] Sending scheduler request to
                                            http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
2005-06-03 11:02:41 [climateprediction.net] Scheduler request to
                                            http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
                                            succeeded
2005-06-03 11:02:41 [climateprediction.net] Message from server: No work sent
2005-06-03 11:02:41 [climateprediction.net] Message from server: (reached daily quota of 4 results)
2005-06-03 11:02:41 [climateprediction.net] No work from project
2005-06-03 11:02:41 [climateprediction.net] Deferring communication with project for 6 hours,
                                            25 minutes, and 37 seconds

Line-By-Line Explanation

Sending scheduler request to '(url)'

The Participant's Computer is asking for more work by submitting a request to the Scheduler.

Scheduler request to '(url)' succeeded

The Scheduler Request succeeded.

Message from server: No work sent

But, no work was sent...

Message from server: (reached daily quota of 'x' results)

Because: The Host has already download the maximum allowed number of Work Units.

No work from project

Results in no work from the Project.

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

Now, we will wait for some interval of time set by the Exponential Back-Off Mechanism.

[edit] Scheduler Request Succeeded - Last RPC Too Recent

2005-06-03 12:30:50 [SETI@home] Sending scheduler request to
                                http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-06-03 12:30:57 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
                                succeeded
2005-06-03 12:31:06 [SETI@home] Sending scheduler request to
                                http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-06-03 12:31:10 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
                                succeeded
2005-06-03 12:31:10 [SETI@home] Message from server: Not sending work - last RPC too recent: 13 sec
2005-06-03 12:31:10 [SETI@home] No work from project
2005-06-03 12:31:10 [SETI@home] Deferring communication with project for 9 minutes and 59 seconds

Line-By-Line Explanation

Sending scheduler request to '(url)'

The Participant's Computer is asking for more work by submitting a request to the Scheduler.

Scheduler request to '(url)' succeeded

The Scheduler Request succeeded.

Note the time!

Sending scheduler request to '(url)'

The Participant's Computer is asking for more work by submitting a request to the Scheduler.

Scheduler request to '(url)' succeeded

The Scheduler Request succeeded.

Message from server: Not sending work - last RPC too recent: 'x' sec

Because: The Host contacted the Scheduler in the recent past, and this request was sent before it should have been sent. Because of this, we will have to wait some more before we can try again to contact the Scheduler.

No work from project

Results in no work from the Project.

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

Now, we will wait for some interval of time set by the Exponential Back-Off Mechanism.

[edit] Scheduler Request Succeeded - No Work Available

2005-03-09 08:46:07 [LHC@home] Sending request to scheduler:
                               http://lhcathome-sched1.cern.ch/scheduler/cgi
2005-03-09 08:46:08 [LHC@home] Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi
                               succeeded
2005-03-09 08:46:08 [LHC@home] Message from server: No work available
2005-03-09 08:46:08 [LHC@home] No work from project
2005-03-09 08:46:08 [LHC@home] Deferring communication with project for 1 hours, 0 minutes,
                               and 0 seconds