Sending scheduler request to '(url)'
From Unofficial BOINC Wiki
Contents |
[edit] General
Message Type: Information Message
This message indicates that the BOINC Daemon is going to contact the Project's Scheduling Server to perform one or more tasks, including (but not limited to):
- Reporting completed Results.
- Requesting new Work Units to process.
- Obtaining new Preference Settings.
- Synchronizing Preference Settings downloaded from another Project.
- Synchronizing the Cross-Project ID.
- Sending a "Trickle" Message
- Note:
- The prefix "HTTPS" only indicates that he Scheduler Request Message is being exchanged with a secure server connection. Most BOINC Powered Projects use the faster though slightly less secure "HTTP" Protocol.
[edit] Alternate Message Formats
- Sending request to scheduler: '(url)'
- Obsolete/Changed in Version: 4.3x
[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] Trickle Message - Success
(1) 2006-01-23 06:49:43 [climateprediction.net] Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi (2) 2006-01-23 06:49:43 [climateprediction.net] Reason: To send trickle-up message (3) 2006-01-23 06:49:43 [climateprediction.net] Note: not requesting new work or reporting results (4) 2006-01-23 06:49:54 [climateprediction.net] Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
Line-By-Line Explanation
- Sending scheduler request to '(url)'
- We create a Scheduler Request Message for a specific project's Scheduling Server.
- Reason: To send trickle-up message
- Because we need to "report" one or more Trickle Messages.
- Note: not requesting new work or reporting results
- We are in no need of work from this project.
- Scheduler request to '(url)' succeeded
- We were able to complete the exchange of Scheduler Request Message and Scheduler Reply Messages.
[edit] Trickle Message - Couldn't Resolve Hostname
(1) 2006-01-23 06:49:18 [climateprediction.net] Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi (2) 2006-01-23 06:49:18 [climateprediction.net] Reason: To send trickle-up message (3) 2006-01-23 06:49:18 [climateprediction.net] Note: not requesting new work or reporting results (4) 2006-01-23 06:49:18 [ ] Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
Line-By-Line Explanation
- Sending scheduler request to '(url)'
- We create a Scheduler Request Message for a specific project's Scheduling Server.
- Reason: To send trickle-up message
- Because we need to "report" one or more Trickle Messages.
- Note: not requesting new work or reporting results
- We are in no need of work from this project.
- Couldn't resolve hostname ['(hostname)']
- Because of one or more network errors we were unable to complete the exchange of Scheduler Request Message and Scheduler Reply Messages.
RSS Feeds
