Scheduler request to '(url)' failed: '(error-text)'

From Unofficial BOINC Wiki

Contents 1 General 2 Alternate Message Formats 3 Example Log(s) 3.1 No Schedulers Responded 3.1.1 Line-By-Line Explanation 3.2 Scheduler Request Failed (-106) 3.2.1 Line-By-Line Explanation 3.3 Scheduler Request Failed - Timeout (-182) 3.4 Scheduler Request Failed: Can't Resolve Host Name 3.5 Scheduler Request to '(url)' Failed:System Fopen 4 Other Related Messages

[edit] General

Message Type: Information Message

This message means that the BOINC Client Software made the connection between the Participant's Computer and the Project's Scheduling Server and that the communication did not succeed and that the required synchronizations and data transfers did not occur with no detected errors.

[edit] Alternate Message Formats

• Scheduler RPC to '(url)' failed

Obsolete/Changed in Version: 4.3x

• Scheduler request to '(url)' failed

Obsolete/Changed in Version: 4.3x

• Scheduler request to '(url)' failed with a return value of '(error-code)'

Obsolete/Changed in Version: 4.72

[edit] Example Log(s)

[edit] No Schedulers Responded

(1) 2005-06-04 00:53:13 [SETI@home] Requesting 21829.03 seconds of work
(2) 2005-06-04 00:53:13 [SETI@home] Sending scheduler request to
                                    http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
(3) 2005-06-04 00:54:28 [SETI@home] Scheduler request to
                                    http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
(4) 2005-06-04 00:54:28 [SETI@home] No schedulers responded
(5) 2005-06-04 00:54:28 [SETI@home] Deferring communication with project for 30 minutes and 10 seconds

Line-By-Line Explanation

1. Requesting "x" seconds of work

   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.

2. Sending request to scheduler: '(url)'

   This message indicates that the BOINC Client Software is making the attempt to connect to the Project's Scheduling Server.

3. Scheduler request to '(url)' failed

   This message indicates that the communications session to the Project's Scheduling Server did not succeed.

4. No schedulers responded

   This message indicates the reason why the communications session with the Project's Scheduling Server did not succeed.

5. 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 contact the Project's Scheduling Server.

[edit] Scheduler Request Failed (-106)

2005-06-28 18:20:48 [SETI@home Beta Test] Scheduler request to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi 
                                          failed with a return value of -106
2005-06-28 18:20:48 [SETI@home Beta Test] No schedulers responded
2005-06-28 18:20:49 [SETI@home Beta Test] Deferring communication with project for 1 hours, 47 minutes, and 57 seconds

Line-By-Line Explanation

• Scheduler request to '(url)' failed with a return value of '(error-code)'

This message indicates the reason why the communications session with the Project's Scheduling Server did not succeed.

• No schedulers responded

That means the Scheduler Request Message was not able to be sent for one reason or another.

• 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 contact the Project's Scheduling Server.

[edit] Scheduler Request Failed - Timeout (-182)

7/8/2005 10:03:31 AM|ProteinPredictorAtHome|Sending scheduler request to
                                            http://predictor.scripps.edu/predictor_cgi/cgi
7/8/2005 10:03:31 AM|ProteinPredictorAtHome|Reason: To fetch work
7/8/2005 10:03:31 AM|ProteinPredictorAtHome|Requesting 4320 seconds of work, returning 0 results
7/8/2005 10:13:31 AM|ProteinPredictorAtHome|Scheduler request to
                                            http://predictor.scripps.edu/predictor_cgi/cgi
                                            failed with a return value of -182
7/8/2005 10:13:31 AM|ProteinPredictorAtHome|No schedulers responded
7/8/2005 10:13:32 AM|ProteinPredictorAtHome|Deferring communication with project for 1 minutes
                                            and 55 seconds

Line-By-Line Explanation

• Sending scheduler request to '(url)'

Starting a communication session with the Project's Scheduler.

• Reason: To fetch work

Te get more work ...

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

Asking for more work without returning any Results.

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

But we failed to complete the request because too much time passed before we got an answer.

• No schedulers responded

Because no Scheduler responded to the Scheduler Request Message.

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

So, we wait a period of time based on Exponential Back-Off, each attempt is tried after a longer and longer delay.

[edit] Scheduler Request Failed: Can't Resolve Host Name

(1) 7/12/2005 11:02:49 AM|SZTAKI Desktop Grid|Sending scheduler request to
                                              http://casca.lpds.sztaki.hu/szdg_cgi/cgi
(2) 7/12/2005 11:02:49 AM|SZTAKI Desktop Grid|Reason: To report results
(3) 7/12/2005 11:02:49 AM|SZTAKI Desktop Grid|Requesting 4320 seconds of work, returning 1 results
(4) 7/12/2005 11:03:04 AM|                   |Can't resolve hostname [casca.lpds.sztaki.hu]
                                              valid name, no data record of requested type
(5) 7/12/2005 11:03:04 AM|SZTAKI Desktop Grid|Scheduler request failed: can't resolve hostname
(6) 7/12/2005 11:03:04 AM|SZTAKI Desktop Grid|Scheduler request to 
                                              http://casca.lpds.sztaki.hu/szdg_cgi/cgi failed:
                                              can't resolve hostname
(7) 7/12/2005 11:03:04 AM|SZTAKI Desktop Grid|Deferring communication with project for 44 seconds

Line-By-Line Explanation

1. Sending scheduler request to '(url)'
   • We are going to send a Scheduler Request Message to the Project.
2. Reason: To report results
   • So we can report the Results that have been processed.
3. Requesting '(seconds)' seconds of work, returning '(count)' results
   • In the Scheduler Request Message we are going to ask for some work and return one Result.
4. [[Can't resolve hostname ['(host-name)'] valid name, no data record of requested type]]
   • Because the DNS "look-up" failed.
5. Scheduler request failed: '(error-text)'
   • With the DNS "look-up" failure, the Scheduler Request failed.
6. Scheduler request to '(url)' failed: '(error-text)'
   • So, we cannot complete the transaction.
7. Deferring communication with project for "x" hours, "y" minutes, and "z" seconds
   • So, use the Exponential Back-Off Mechanism to pause before we will try again.

[edit] Scheduler Request to '(url)' Failed:System Fopen

Unhide the directory you run the BOINC Client Software from. The "system fopen" message is when the BOINC Client Software can't determine where it is running from. If you are running Linux then you may want to try this start-up script or one of these scripts. If you are running Windows XP, and you have hidden the BOINC folder, unhiding it will resolve this error.

(1) Scheduler request to http:/setboinc.ssl.berkeley.edu/sah_cgi:cgi failed:system fopen

Line-By-Line Explanation

1. Scheduler request to '(url)' failed: '(error-text)'

• Because the BOINC Client Software is unable to locate the directory from which it was started, the BOINC Client Directory, the files necessary to communicate with a Scheduler cannot be created.

[edit] Other Related Messages

• Scheduler request to '(url)' failed
• Scheduler request to '(url)' succeeded
• Scheduler RPC to '(url)' failed (Obsolete/Changed in Version 4.3x)
• Scheduler RPC to '(url)' succeeded (Obsolete/Changed in Version 4.3x)