Master file parse failed
From Unofficial BOINC Wiki
Contents |
[edit] General
Message Type: Warning Message
The BOINC Client Software is not able to parse the Master File that was received, and thus cannot obtain the list of Schedulers for the Project.
This is likely to be as a result of the BOINC Client Software receiving a corrupt Master File and the operation to retry retrieving the master file will commence at the next communication interval.
Other cases exist where the Project is ended and the Scheduler information embedded within the Master File is removed. This is the case with most of the messages related to Pirates@Home.
[edit] Version Information
- None.
[edit] Example Log
[edit] Master Page Has No Schedulers
2005-06-25 10:21:55 [Pirates@Home] Master file parse failed
2005-06-25 10:21:55 [Pirates@Home] Master page has no schedulers
2005-06-25 10:21:56 [Pirates@Home] Deferring communication with project for 5 days, 1 hours,
56 minutes, and 9 seconds
Line-By-Line Explanation
- Master file parse failed
- Parsing of the Master Page failed.
- The cause of the failure was the lack of the Scheduler information on the Master Page.
- This Message indicates that we will use the Exponential Back-Off Mechanism to calculate a time interval to wait before attempting to make another try to download the Master Page from the Project's Web Server.
[edit] Too Many Backoffs - Fetching Master File
2005-06-26 23:46:03 [Pirates@Home] Fetching master file
2005-06-26 23:46:04 [Pirates@Home] Master file parse failed
2005-06-26 23:46:04 [Pirates@Home] Too many backoffs - fetching master file
2005-06-26 23:46:05 [Pirates@Home] Deferring communication with project for 2 days, 16 hours,
17 minutes, and 48 seconds
Line-By-Line Explanation
- We are going to do a Scheduler RPC to obtain the Master File from the Project's Web Site.
- Master file parse failed
- The Master File failed to parse for one or more reasons.
- Because of the number of times we tried to work with the Master Page exceeds the error bounds, we will obtain a fresh copy after the time required for the Exponential Back-Off has expired.
- And now we wait for a brief span of time, I mean, heck, it is only 2 days ...
[edit] Could Not Contact Any Schedulers
2005-05-26 10:56:55 [Pirates@Home] Master file parse failed 2005-05-26 10:56:55 [Pirates@Home] Could not contact any schedulers for http://pirates.vassar.edu/ 2005-05-26 10:56:55 [Pirates@Home] Deferring communication with project for 1 minutes and 0 seconds
Line-By-Line Explanation
- Master file parse failed
- Parsing of the Master Page failed.
- The Master File did have address information for the Project's Schedulers, but we were unable to contact any of the Schedulers.
- This Message indicates that we will use the Exponential Back-Off Mechanism to calculate a time interval to wait before attempting to make another try to download the Master Page from the Project's Web Server.
[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
RSS Feeds
