Init op project failed, error '(error-code)'

From Unofficial BOINC Wiki

Contents 1 General 2 Version Information 3 Example Log(s) 3.1 Can't Resolve Hostname - No Record 3.1.1 Line-By-Line Explanation 3.2 Init Op Project Failed, Error -108 3.2.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 failed to contact the Server, usually the Scheduling Server and this message indicates the following:

1. The internal module of the BOINC Client Software where the error occurred,
2. an error number.

The error number is of limited use to the Participant but it may be of interest to the Developers if you are reporting the error.

[edit] Version Information

• None.

[edit] Example Log(s)

[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] Init Op Project Failed, Error -108

This sequence of messages occurred because the Participant's Computer did not have the proper permissions set on the BOINC Directory and the sub-directories.

2005-07-07 22:58:19 [                      ] Resuming computation and network activity
2005-07-07 22:58:19 [                      ] request_reschedule_cpus: Resuming activities
2005-07-07 22:58:21 [SETI@home] Scheduler request initialization to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed, error -108
2005-07-07 22:58:21 [SETI@home             ] Deferring communication with project for 57 seconds
2005-07-07 22:58:26 [ProteinPredictorAtHome] Scheduler request initialization to
http://predictor.scripps.edu/predictor_cgi/cgi failed, error -108
2005-07-07 22:58:26 [ProteinPredictorAtHome] init_op_project failed, error -108
2005-07-07 22:58:26 [ProteinPredictorAtHome] Deferring communication with project for 1 minutes
and 0 seconds
2005-07-07 22:59:09 [                      ] request_reschedule_cpus: project op

Line-By-Line Explanation

• Resuming computation and network activity

We were suspended for any number of reasons, but now we can go back to work.

• request_reschedule_cpus: Resuming activities

Because we have nothing going on, reschedule the CPUs.

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

Unable to write to a file or directory we cannot make a Scheduler Request Message. If we cannot make the message file to send, then we can't initialize the communication session.

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

So we use the Exponential Back-Off Mechanism to wait a bit.

Meanwhile lets try another Project.

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

Unable to write to a file or directory we cannot make a Scheduler Request Message. If we cannot make the message file to send, then we can't initialize the communication session.

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

Two strikes! We cannot initialize and start processing Results for a Project because we do not have any, and we cannot get any because we cannot make a Scheduler Request Message.

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

So we use the Exponential Back-Off Mechanism to wait a bit.

• request_reschedule_cpus: project op

Because we did not have a successful start of work on any Project, we have to schedule the CPUs which means we have to get work ...

From this point forward, the cycle of messages will repeat forever. The BOINC Client Software must have the ability to read and write files within the BOINC Directory and all of the sub-directories.

[edit] Other Related Messages

• None.

[edit] Also See

• Error Code