Name | 8hHMDmQmfg7n9Rq4apOajLDm4fhM0noT9bVof3QYDm8YYKDmbkzq9n_1 |
Workunit | 232817767 |
Created | 3 Jun 2025, 13:46:47 UTC |
Sent | 3 Jun 2025, 14:57:56 UTC |
Report deadline | 11 Jun 2025, 14:57:56 UTC |
Received | 3 Jun 2025, 15:36:34 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Compute error |
Exit status | 1 (0x00000001) Unknown error code |
Computer ID | 10852355 |
Run time | 12 sec |
CPU time | |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 35.77 GFLOPS |
Application version | ATLAS Simulation v3.01 (vbox64_mt_mcore_atlas) x86_64-pc-linux-gnu |
Peak working set size | 3.27 MB |
Peak swap size | 4.72 MB |
Peak disk usage | 205.36 MB |
<core_client_version>7.20.5</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2025-06-03 16:58:08 (207264): Detected: vboxwrapper 26206 2025-06-03 16:58:08 (207264): Detected: BOINC client v7.20.5 2025-06-03 16:58:13 (207264): Error in guest additions for VM: -1041038848 Command: VBoxManage -q list systemproperties Output: VBoxManage: error: Failed to create the VirtualBox object! VBoxManage: error: Code NS_ERROR_SOCKET_FAIL (0xC1F30200) - IPC daemon socket error (extended info not available) VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start. 2025-06-03 16:58:13 (207264): Detected: VirtualBox VboxManage Interface (Version: 7.0.20) 2025-06-03 16:58:18 (207264): Error in host info for VM: -1041038848 Command: VBoxManage -q list hostinfo Output: VBoxManage: error: Failed to create the VirtualBox object! VBoxManage: error: Code NS_ERROR_SOCKET_FAIL (0xC1F30200) - IPC daemon socket error (extended info not available) VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start. 2025-06-03 16:58:18 (207264): WARNING: Communication with VM Hypervisor failed. 2025-06-03 16:58:18 (207264): ERROR: VBoxManage list hostinfo failed 16:58:18 (207264): called boinc_finish(1) </stderr_txt> ]]>
©2025 CERN