Scheduler list fetch failed
From Unofficial BOINC Wiki
Contents |
[edit] General
Message Type: Information Message
This Message means that the BOINC Client Software was not able to start a communication session with the Project because it was unable to obtain the most up-to-date copy of the Project's Master Page. The other Messages that accompany this message will contain the details of the specific cause of the failure.
This message means that the BOINC Client Software when attempting to contact the Project's Scheduling Server could not get the actual address because the Web Page at Project's Master URL of the Project's Web Site was not available. The reason that the Scheduling Server is contacted indirectly is so that the movement of the Servers can take place and the only update that is required is to the Project's Web Site where they change a comment field. With a direct connection, each change in an address for a Server would require that all of the Participants have to make a change on their system, or the Project never moves a Server to a new address (and how likely is that!).
The most common causes of this error is when your Internet connection has failed or the Project's Web Server is off-line.
Another cause is when the site is under heavy load (I just experienced this one with LHC@Home = {050223} when they restarted the Project).
[edit] Version Information
[edit] Alternate Message Formats
- Master file fetch failed
- Master page fetch failed
[edit] Example Log(s)
[edit] Couldn't Start Master Page Download (-107)
2005-06-27 01:11:16 [LHC@home alpha] Couldn't start master page download: -107 2005-06-27 01:11:16 [LHC@home alpha] Master page fetch failed 2005-06-27 01:11:16 [LHC@home alpha] Deferring communication with project for 1 minutes and 0 seconds
Line-By-Line Explanation
- Unable to download the Master Page.
- Causing a "Master Page Fetch Error", because the Project's Web Site was not available.
- So now we will use Exponential Back-Off to calculate a time interval to wait before attempting to make another try to contact the Project's Scheduling Server.
[edit] Couldn't Start Master Page Download (-113)
2005-06-29 04:35:12 [ ] Can't resolve hostname [lhcathome-alpha.cern.ch] valid name,
no data record of requested type
2005-06-29 04:35:12 [LHC@home alpha] Couldn't start master page download: -113
2005-06-29 04:35:12 [LHC@home alpha] Master page fetch failed
2005-06-29 04:35:12 [LHC@home alpha] Deferring communication with project for 1 minutes and 0 seconds
Line-By-Line Explanation
- And fail to make the connection because the BOINC Client Software cannot find a translation of the URL into an IP Address.
- Unable to download the Master Page.
- Causing a "Master Page Fetch Error", because the Project's Web Site was not available.
- So now we will use Exponential Back-Off to calculate a time interval to wait before attempting to make another try to contact the Project's Scheduling Server.
[edit] Master File Fetch Failed
In this example the Project's Web Server is the Server that is Off-Line at the moment. This means that the exact messages are slightly different. The end result is the same as you cannot perform the upload of the Result Data File.
5/23/2005 9:32:43 PM| |Can't resolve hostname [climateprediction.net]
(valid name, no data record of requested type)
5/23/2005 9:32:43 PM|climateprediction.net|Couldn't read master page for climateprediction.net:
error -113
5/23/2005 9:32:43 PM|climateprediction.net|Master file fetch failed
5/23/2005 9:32:44 PM|climateprediction.net|Deferring communication with project for 58 seconds
Line-By-Line Explanation
- This message tells you that the normal mechanisms that translate human usable addresses (like a URL into the actual IP Addresses that are used by the computers.
- This line tells you that the BOINC Client Software was unable to contact the Climateprediction.net's Web Server.
- This message is telling you that the Web Page that is at the Project's Master URL was not available.
- The BOINC Client Software is going to wait for a short interval of time, calculated using the Exponential Back-Off. And in this case, the time is very short. Be advised that it goes up pretty fast!
[edit] Other Related Messages
- Can't open master file
- Couldn't read master page for '(project identifier)': error '(error-code)'
- Couldn't start download of scheduler list: '(error-text)'
- Obsolete: Couldn't start master page download: '(error-code)'
- Obsolete: Couldn't start master page download: '(error-text)'
- Fetching scheduler list
- Obsolete: Fetching master file
- Obsolete: Fetching master page
- Scheduler list fetch failed
- Obsolete: Master file fetch failed
- Obsolete: Master page fetch failed
- Master file parse failed
- Master page download succeeded
- Master page has no schedulers
- Scheduler op: init_master_fetch failed.
- Too many backoffs - fetching master file
[edit] Developer Information
| Code Location: | boinc/client/scheduler_op.C |
| Function: | SCHEDULER_OP::check_master_fetch_start() |
| 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
