Couldn't read master page for '(project identifier)': error '(error-code)'

From Unofficial BOINC Wiki

Jump to: navigation, search

Contents

[edit] General

Message Type: Warning Message

This Message means that the BOINC Client Software was unable to locate the "Master Page" when using the Project's Master URL because of a network problem. There are many causes for this error, to include:

More details on Error Codes can give you a better idea of why the failure occurred.

[edit] Version Information

[edit] Message Added

New in BOINC Client Software Version: 4.46

[edit] Alternate Message Formats

  • Couldn't read master page for '(project identifier)': error '(error-code)'
Obsolete/Changed in Version: 4.46
Because the message is entered into the log with the Project Name the Project's Master URL is not required.

[edit] Example Log(s)

[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.
  • Couldn't read master page for '(project identifier)': error '(error-code)'
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] Can't Resolve Hostname - Host Not Found

Note:
In this log example, I tried to attach to a Project with a "bogus" URL, just to make this set of messages ... but this is still the error you would get regardless of the reason that the URL is bad.
2005-06-03 02:51:27 [                              ] Can't resolve hostname [climateprediction.net1]
                                                     host not found
2005-06-03 02:51:27 [http://climateprediction.net1/] Couldn't read master page for          
                                                     http://climateprediction.net1/: 
                                                     error -113
2005-06-03 02:51:27 [http://climateprediction.net1/] Detaching from project - check for URL error
                                                     BOINC couldn't get main page for 
                                                     http://climateprediction.net1/.
                                                     Please check the URL and try again.
2005-06-03 02:51:27 [http://climateprediction.net1/] Resetting project
2005-06-03 02:51:27 [http://climateprediction.net1/] Detaching from project

Line-By-Line Explanation

The "host-name" used is in error, usually caused by incorrect typing or copying of the URL when "Attaching" the BOINC Client Software to a BOINC Powered Project.
  • Couldn't read master page for '(project identifier)': error '(error-code)'
Because the Project's Master URL was wrong, the Project's Master Page could not be read.
Please check the URL and try again.
The BOINC Client Software is offering a hint as to the problem.
And, because of that, we have to "Detach" From The Project, which includes a Project "Reset".

[edit] Scheduler Request Failed HTTP Insert (-113)

This error means of course that the BOINC Client Software was unable to resove the Project's Host name (convert the text into an IP Address).

2005-06-11 05:51:52 [BURP] Scheduler request to http://burp.boinc.dk/burp_cgi/cgi succeeded
2005-06-11 05:51:52 [BURP] No work from project
2005-06-11 05:51:53 [BURP] Deferring communication with project for 18 minutes and 36 seconds
-+-+/\/\/\/\/\ Log Break /\/\/\/\/\-+-+-
2005-06-11 06:10:30 [BURP] Sending scheduler request to http://burp.boinc.dk/burp_cgi/cgi
2005-06-11 06:10:30 [BURP] Requesting 8640 seconds of work, returning 0 results
2005-06-11 06:10:32 [    ] Can't resolve hostname [burp.boinc.dk] host name not found
2005-06-11 06:10:32 [BURP] Scheduler request failed HTTP insert: -113
2005-06-11 06:10:32 [BURP] Scheduler request initialization to http://burp.boinc.dk/burp_cgi/cgi
failed, error -113
2005-06-11 06:10:32 [BURP] init_op_project failed, error -113
2005-06-11 06:10:32 [BURP] Deferring communication with project for 1 minutes and 0 seconds
2005-06-11 06:11:32 [    ] Can't resolve hostname [burp.boinc.dk] host name not found
2005-06-11 06:11:32 [BURP] Couldn't read master page for BURP: error -113
2005-06-11 06:11:32 [BURP] Master file fetch failed
2005-06-11 06:11:32 [BURP] Deferring communication with project for 1 minutes and 0 seconds
-+-+/\/\/\/\/\ Log Break /\/\/\/\/\-+-+-
2005-06-11 08:19:42 [BURP] Sending scheduler request to http://burp.boinc.dk/burp_cgi/cgi
2005-06-11 08:19:42 [BURP] Requesting 8640 seconds of work, returning 0 results
2005-06-11 08:19:43 [BURP] Scheduler request to http://burp.boinc.dk/burp_cgi/cgi succeeded
2005-06-11 08:19:43 [BURP] No work from project

Line-By-Line Explanation

And in this case we had success! Unfortunately ...
No work available, so lets wait ...
Now, we will wait for some interval of time set by the Exponential Back-Off Mechanism, only to have the wheels start to come off the wagon ...
Now we are again asking for more work by submitting a request to the Scheduler.
And asking for 8,640 seconds worth of work ...
But now the Server cannot be found!
And this causes an error in the creation of the Scheduler Request Message...
With our previous error, we did not complete the initialization of the communication session with the Scheduler.
And we exit the communication process; to then wait ...
Now, we will wait for some interval of time set by the Exponential Back-Off Mechanism.
And we still cannot locate the Server. But now we have a new problem ...
  • Couldn't read master page for '(project identifier)': error '(error-code)'
With the Server off-line, the Master Page can't be found ...
Causing a "fetch" failure ...
Later ...
And in this case we had success! Unfortunately ...
No work available, so we will have to wait again ...


[edit] Trouble-Shooting

[edit] Other Related Messages

[edit] Also See

Personal tools
RSS Feeds
BOINC Wiki RSS feeds RSS Feeds
Powered by BOINC!
Powered by BOINC