Scheduler request failed HTTP insert: '(error-code)'

From Unofficial BOINC Wiki

Contents 1 General 2 Version Information 2.1 Alternate Message Formats 3 Example Log(s) 3.1 Scheduler Request Failed HTTP Insert (-107) 3.1.1 Line-By-Line Explanation 3.2 Scheduler Request Failed HTTP Insert (-113) 3.2.1 Line-By-Line Explanation 3.3 Can't Resolve Hostname - No Record 3.3.1 Line-By-Line Explanation 3.4 Can't Resolve Hostname - Host Not Found or Server Failure 3.4.1 Line-By-Line Explanation 4 Other Related Messages 5 Also See

[edit] General

Message Type: Warning Message

This Message means that the BOINC Client Software was attempting to communicate to the Project's Scheduling Server but encountered an error as it was creating the Scheduler Request Message for sending to the Scheduler.

This error should not be common, in one of the log examples ("Scheduler Request Failed HTTP Insert"), the error occurred apparently because the Scheduler Request Message was being sent just as the Project was taking the Scheduling Server down for maintenance or it failed.

This message contains the following:

1. specific URL which the BOINC Client Software was unable to contact, and
2. an error number.

[edit] Version Information

[edit] Alternate Message Formats

• Scheduler init op project to '(scheduler-url)' failed, error '(error-code)'

Obsolete/Changed in Version: 4.4x

[edit] Example Log(s)

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

This error means of course that the BOINC Client Software was unable to contact the Project's Server.

2005-06-27 01:11:16 [SETI@home Beta Test] Scheduler request failed HTTP insert: -107
2005-06-27 01:11:16 [SETI@home Beta Test] Scheduler request initialization to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi failed, error -107
2005-06-27 01:11:16 [SETI@home Beta Test] init_op_project failed, error -107
2005-06-27 01:11:17 [SETI@home Beta Test] Deferring communication with project for 1 hours, 20 minutes, and 36 seconds

Line-By-Line Explanation

• Scheduler request failed HTTP insert: '(error-code)'

And this causes an error in the creation of the Scheduler Request Message...

• Scheduler request initialization to '(url)' failed, error '(error-code)'

With our previous error, we did not complete the initialization of the communication session with the Scheduler.

• Init_op_project failed, error '(error-code)'

And we exit the communication process, reporting the error again; to then wait ...

• Deferring communication with project for "x" hours, "y" minutes, and "z" seconds

Now, we will wait for some interval of time set by the Exponential Back-Off Mechanism.

[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

• Scheduler request to '(url)' succeeded

And in this case we had success! Unfortunately ...

• No work from project

No work available, so lets wait ...

• Deferring communication with project for "x" hours, "y" minutes, and "z" seconds

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 ...

• Sending request to scheduler: '(url)'

Now we are again asking for more work by submitting a request to the Scheduler.

• Requesting '(seconds)' seconds of work, returning '(count)' results

And asking for 8,640 seconds worth of work ...

• Can't resolve hostname '(host-name)' host name not found

But now the Server cannot be found!

• Scheduler request failed HTTP insert: '(error-code)'

And this causes an error in the creation of the Scheduler Request Message...

• Scheduler request initialization to '(url)' failed, error '(error-code)'

With our previous error, we did not complete the initialization of the communication session with the Scheduler.

• Init_op_project failed, error '(error-code)'

And we exit the communication process; to then wait ...

• Deferring communication with project for "x" hours, "y" minutes, and "z" seconds

Now, we will wait for some interval of time set by the Exponential Back-Off Mechanism.

• Can't resolve hostname '(host-name)' host name not found

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 ...

• Master file fetch failed

Causing a "fetch" failure ...

Later ...

• Scheduler request to '(url)' succeeded

And in this case we had success! Unfortunately ...

• No work from project

No work available, so we will have to wait again ...

[edit] Can't Resolve Hostname - No Record

6/4/2005 4:29:28 PM|http://setiathome.berkeley.edu/|Requesting 432000.00 seconds of work
6/4/2005 4:29:28 PM|http://setiathome.berkeley.edu/|Sending request to scheduler:
                                                    http://setiathome.berkeley.edu/
6/4/2005 4:29:28 PM|                               |Can't resolve hostname 
                                                    [setiboinc.ssl.berkeley.edu] 
                                                    (valid name, no data record of requested type)
6/4/2005 4:29:28 PM|http://setiathome.berkeley.edu/|scheduler init_op_project to
                                                    http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
                                                    failed, error -113
6/4/2005 4:29:28 PM|http://setiathome.berkeley.edu/|init_op_project failed,
                                                    error -113            
6/4/2005 4:29:29 PM|http://setiathome.berkeley.edu/|Deferring communication with project for
                                                    59 seconds

Line-By-Line Explanation

• Requesting "x" seconds of work

The reason we are going to make a Scheduler Request.

• Sending request to scheduler: '(url)'

We make the attempt to contact the Scheduler.

• Can't resolve hostname ['(host-name)'] (valid name, no data record of requested type)

And fail to make the connection because the BOINC Client Software cannot find a translation of the URL into an IP Address.

• scheduler init_op_project to '(scheduler-url)' failed, error '(error-code)'

This message indicates the exact stage when the error occurred during the communication process with the Project's Scheduler.

• init_op_project failed, error '(error-code)'

And we exit the communication process.

• Deferring communication with project for "x" hours, "y" minutes, and "z" seconds

This message indicates that we will use Exponential Back-Off to calculate a time interval to wait before attempting to make another try to upload the file to the Project's Scheduling Server.

[edit] Can't Resolve Hostname - Host Not Found or Server Failure

2004-08-18 04:45:01 [---] Can't resolve hostname climateapps2.oucs.ox.ac.uk 
                          (host not found or server failure)
2004-08-18 04:45:01 [climateprediction.net] scheduler init_op_project to
                                            http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
                                            failed, error -113
2004-08-18 04:45:01 [climateprediction.net] Deferring communication with project for
                                            1 minutes and 0 seconds

Line-By-Line Explanation

• Can't resolve hostname '(host-name)' (host not found or server failure)

The error indicating that the Host is among the missing.

• scheduler init_op_project to '(scheduler-url)' failed, error '(error-code)'

This message indicates the exact stage when the error occurred during the communication process with the Project's Scheduler.

• Deferring communication with project for "x" hours, "y" minutes, and "z" seconds

This message indicates that we will use Exponential Back-Off to calculate a time interval to wait before attempting to make another try to upload the file to the Project's Scheduling Server.

[edit] Other Related Messages

• None.

[edit] Also See

• Error Code