Name | VP9KDmfXOe7n9Rq4apOajLDm4fhM0noT9bVof3QYDm1ySKDmIEBFvn_1 |
Workunit | 232657504 |
Created | 28 May 2025, 8:47:10 UTC |
Sent | 28 May 2025, 11:28:25 UTC |
Report deadline | 5 Jun 2025, 11:28:25 UTC |
Received | 28 May 2025, 13:24:33 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Compute error |
Exit status | 1 (0x00000001) Unknown error code |
Computer ID | 10822464 |
Run time | 13 sec |
CPU time | |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 8.49 GFLOPS |
Application version | ATLAS Simulation v3.01 (vbox64_mt_mcore_atlas) x86_64-pc-linux-gnu |
Peak working set size | 3.44 MB |
Peak swap size | 5.05 MB |
Peak disk usage | 216.28 MB |
<core_client_version>7.18.1</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2025-05-28 14:24:27 (2034391): Detected: vboxwrapper 26206 2025-05-28 14:24:27 (2034391): Detected: BOINC client v7.18.1 2025-05-28 14:24:33 (2034391): 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-05-28 14:24:33 (2034391): Detected: VirtualBox VboxManage Interface (Version: 6.1.38) 2025-05-28 14:24:38 (2034391): 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-05-28 14:24:38 (2034391): WARNING: Communication with VM Hypervisor failed. 2025-05-28 14:24:38 (2034391): ERROR: VBoxManage list hostinfo failed 14:24:38 (2034391): called boinc_finish(1) </stderr_txt> ]]>
©2025 CERN