Failed to stop applications; aborting CPU benchmarks

From Unofficial BOINC Wiki

Contents 1 General 2 Version Information 2.1 Alternate Message Formats 3 Example Log 3.1 Aborting CPU Benchmarks 3.1.1 Line-By-Line Explanation 3.2 Aborting CPU Benchmarks - No Tasks Start 3.2.1 Line-By-Line Explanation 3.2.2 Action 4 Other Related Messages 5 Developer Information 6 Also See

[edit] General

Message Type: Error Message

This message means that the BOINC Client Software attempted to start running the CPU Benchmark routine but was unable to do so because one of the Science Applications did not stop running soon enough. This can occur for some of the Science Applications that take a fairly long time to start-up or shut-down. The Science Application for the Climateprediction.net Project can do this on occasion.

[edit] Version Information

[edit] Alternate Message Formats

• Aborting CPU benchmarks, one or more active tasks are still running

[edit] Example Log

[edit] Aborting CPU Benchmarks

6/6/2005 8:43:20 AM||Running CPU benchmarks
6/6/2005 8:43:28 AM||Aborting CPU benchmarks, one or more active tasks are still running.
6/6/2005 8:43:28 AM||Resuming computation and network activity

Line-By-Line Explanation

• Running CPU benchmarks

This message indicates the beginning of the Benchmark process. The BOINC Daemon will issue commands to the currently running Science Applications which then have to Checkpoint and halt operation.

• Aborting CPU benchmarks, one or more active tasks are still running

After the time interval allowed for the Science Applications to halt operation has expired, if the BOINC Daemon finds one or more active tasks still running, the BOINC Daemon will give up and re-start normal operations.

• Resuming computation and network activity

Ok, back in business.

[edit] Aborting CPU Benchmarks - No Tasks Start

However, watch out for a situation where the tasks may have ended after the abort, and no task is started.

17/07/2005 16:05:48|climateprediction.net|Pausing result 45z1_000294637_0 (removed from memory)
17/07/2005 16:05:50||Running CPU benchmarks
17/07/2005 16:05:58||Aborting CPU benchmarks, one or more active tasks are still running.
17/07/2005 16:05:58||Resuming computation and network activity
17/07/2005 16:05:58||request_reschedule_cpus: Resuming activities
17/07/2005 16:05:58||request_reschedule_cpus: process exited

Line-By-Line Explanation

• Pausing result '(result)' (removed from memory)

Pause project to run the benchmark

• Running CPU benchmarks

This message indicates the beginning of the Benchmark process. The BOINC Daemon will issue commands to the currently running Science Applications which then have to Checkpoint and halt operation.

• Aborting CPU benchmarks, one or more active tasks are still running

After the time interval allowed for the Science Applications to halt operation has expired, if the BOINC Daemon finds one or more active tasks still running, the BOINC Daemon will give up and re-start normal operations.

• Resuming computation and network activity

Ok, should be back in business.

• request_reschedule_cpus: Resuming activities

Resuming activities so we need to schedule the CPUs.

• request_reschedule_cpus: process exited

The process has finally exited after the resumption. This can be a problem leaving your computer doing nothing.

Action

If your processor is doing nothing after these messages, exit the BOINC Client Software and restart it.

This problem started with version 4.45. Versions 4.45b and versions 5.2.1 upward appear to have fixed it.

[edit] Other Related Messages

• Aborting CPU benchmarks, one or more active tasks are still running (Obsolete)
• Benchmark results:
• CPU benchmarks timed out, using default values
• Failed to stop applications; aborting CPU benchmarks
• Finished CPU benchmarks
• Number of CPUs: '(Nbr of CPUs)'
• Number of usable CPUs has changed. Running benchmarks.
• Pausing result '(result)' (removed from memory)
• Resuming computation and network activity
• Running CPU benchmarks
• Suspending computation and network activity - running CPU benchmarks
• Version Change Detected (x.y -> x1.y1); running CPU benchmarks
• XXXX double precision MIPS (Whetstone) per CPU
• YYYY integer MIPS (Dhrystone) per CPU

[edit] Developer Information

Code Location:	boinc/client/cs_benchmark.C
Function:	CLIENT_STATE::cpu_benchmarks_poll()
Documentation:	boinc/client/cs_benchmark.C
CVS Extract:	cvs -d :pserver:anonymous:@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout boinc/client/cs_benchmark.C

[edit] Also See

• Wikipedia: Benchmark
• Wikipedia: Dhrystone Benchmark
• Wikipedia: Whetstone Benchmark