Requesting "x" seconds of new work
From Unofficial BOINC Wiki
(Redirected from Requesting "x" seconds of work)
Contents |
[edit] General
Message Type: Information Message
This message means that the BOINC Client Software needs to obtain additional Work Units to fill its Work Buffer so you will not "run dry" and your computer is always going to be busy. The number of seconds that it is going to request will (or should) match up to the number of days of work that you desire and has been set in your Preference Settings.
The BOINC Client Software will attempt to obtain work from the Project where the Long Term Debt is the highest. Failing that, it will go to the Project that has the next highest Long Term Debt. It will also attempt to keep an interesting assortment of work on your local client.
[edit] Alternate Message Formats
- New in Version: 4.45; replaced in 5.2.x by:
- New in 5.2.x
[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
- 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.
- 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.
- This message indicates that the BOINC Client Software is making the attempt to connect to the Project's Scheduling Server.
- 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
- 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.
- 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.
- This message indicates that the BOINC Client Software is making the attempt to connect to the Project's Scheduling Server.
- This message tells you that the communication session did not complete without error.
- 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.
- 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] Requesting "x" Seconds Of New Work
(1) 2005-10-16 19:43:49 [Einstein@Home] Sending scheduler request to
http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
(2) 2005-10-16 19:43:49 [Einstein@Home] Reason: To fetch work
(3) 2005-10-16 19:43:49 [Einstein@Home] Requesting 172800 seconds of new work
(4) 2005-10-16 19:43:55 [Einstein@Home] Scheduler request to
http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
succeeded
Line-By-Line Explanation
- Sending scheduler request to '(url)'
- The BOINC Daemon is sending a Scheduler Request Message to the Project's Scheduling Server.
- Reason: To fetch work
- And the reason for this contact is to obtain more work for the Participant's Computer.
- Requesting "x" seconds of new work
- And we want quite a bit of work ... 4 days worth of work ...
- Scheduler request to '(url)' succeeded
- And we were sucessful in contacting the Project's Scheduling Server.
[edit] Developer Information
| Code Location: | boinc/client/scheduler_op.C |
| Function: | SCHEDULER_OP::start_rpc(PROJECT* p) |
| Documentation: | boinc/client/scheduler_op.C |
| CVS Extract: | cvs -d :pserver:anonymous:@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout boinc/client/scheduler_op.C |
RSS Feeds
