Request reschedule cpus: start failed

From Unofficial BOINC Wiki

Contents 1 General 2 Version Information 3 Example Log(s) 3.1 Start/Restart Failed - Failed To Open File 3.1.1 Line-By-Line Explanation 4 Other Related Messages 4.1 Work Scheduler Messages (General) 4.2 "Trigger" Messages 4.3 Work Fetch Policy Messages 4.4 Work Schedule Policy Messages 5 Also See 6 Developer Information

[edit] General

Message Type: Information Message

This Message means that the BOINC Client Software has tried to start processing a Work Unit with a Science Application but the program failed to start processing.

[edit] Version Information

• None.

[edit] Example Log(s)

[edit] Start/Restart Failed - Failed To Open File

This error set was caused by an error in the permissions on a "slot" within the "slots" directory making it inaccessible by the BOINC Daemon.

2005-07-07 22:56:40 [SETI@home] Resuming computation for result 15au03aa.174.33473.548578.42_2 using
                                setiathome version 4.18
2005-07-07 22:56:42 [SETI@home] Failed to open core-to-app prefs file slots/0/init_data.xml
2005-07-07 22:56:42 [SETI@home] ACTIVE_TASKS::restart_tasks(); restart failed: -108
2005-07-07 22:56:42 [SETI@home] Unrecoverable error for result 15au03aa.174.33473.548578.42_2 
                                (Couldn't restart the app for this result: -108)
2005-07-07 22:56:42 [         ] Resuming computation and network activity
2005-07-07 22:56:42 [         ] request_reschedule_cpus: Resuming activities
2005-07-07 22:56:47 [SETI@home] Failed to open core-to-app prefs file slots/0/init_data.xml
2005-07-07 22:56:47 [         ] request_reschedule_cpus: start failed
2005-07-07 22:56:48 [SETI@home] Deferring communication with project for 52 seconds
-+-+/\/\/\/\/\ Log Break /\/\/\/\/\-+-+-
2005-07-07 22:56:51 [SETI@home] Computation for result 15au03aa.174.33473.548578.42_2 finished
2005-07-07 22:56:51 [SETI@home] Started upload of 15au03aa.174.33473.548578.42_2_0
2005-07-07 22:57:08 [SETI@home] Finished upload of 15au03aa.174.33473.548578.42_2_0
2005-07-07 22:57:08 [SETI@home] Throughput 38777 bytes/sec
2005-07-07 22:57:12 [SETI@home] Couldn't delete file 
                                projects/setiathome.berkeley.edu/15au03aa.174.33473.548578.42_2_0

Line-By-Line Explanation

• Resuming computation for result '(result)' using '(science application)' version '(version)'

Lets get to work, restart a Result.

• Failed to open core-to-app prefs file '(file)'

We cannot access the file needed to start again.

• ACTIVE_TASKS::restart_tasks(); restart failed: '(error-code)'

We failed the restart.

• Unrecoverable error for result '(result)' (Couldn't restart the app for this result: '(error-code)')

Causing an unrecoverable error

• Resuming computation and network activity

As we were in the midst of resuming activity

• request_reschedule_cpus: Resuming activities

Which meant we scheduled the CPUs because we were resuming.

• Failed to open core-to-app prefs file

The task we tried to start could not access a required file (write access).

• request_reschedule_cpus: start failed

Forcing a CPU scheduling event because the start/restart failed.

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

We were unable to contact the Project's Data Server so use Exponential Back-Off to wait a moment.

• Computation for result '(result)' finished

Rats! We cannot continue this Result because of the error.

• Started upload of '(file)'

The BOINC Daemon initiated an upload action with the SETI@Home Project.

• Finished upload of '(file)'

The BOINC Daemon completed the data transfer to the Project's Data Server.

• Throughput 'x' bytes/sec

The measured speed of transfer, in this case was an 38,777 bytes per second.

• Couldn't delete file '(file-name)'

In this case we also cannot delete the file as we cannot access the directory for write/delete activities.

[edit] Other Related Messages

[edit] Work Scheduler Messages (General)

• request_reschedule_cpus: exit_tasks
• request_reschedule_cpus: files downloaded
• request_reschedule_cpus: process exited
• request_reschedule_cpus: project op
• request_reschedule_cpus: Resuming activities
• request_reschedule_cpus: start failed
• schedule_cpus: time '(x.y)'

[edit] "Trigger" Messages

• Computer is over committed
• Less than 1 day until deadline
• Deadline is before reconnect time

[edit] Work Fetch Policy Messages

• Allowing work fetch again.
• Suspending work fetch because computer is overcommitted.

[edit] Work Schedule Policy Messages

• Resuming round-robin CPU scheduling.
• Using earliest-deadline-first scheduling because computer is overcommitted.

[edit] Also See

• Work Scheduler

[edit] Developer Information

Code Location:	boinc/client/cs_apps.C
Function:	CLIENT_STATE::schedule_cpus() CLIENT_STATE::request_schedule_cpus(const char* where)
Documentation:	boinc/client/cs_apps.C
CVS Extract:	cvs -d :pserver:anonymous:@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout boinc/client/cs_apps.C