Name | 0mfNDm9jW16nsSi4ap6QjLDmwznN0nGgGQJmkKkKDm28SKDm4GUIYn_0 |
Workunit | 230252000 |
Created | 10 Feb 2025, 0:22:43 UTC |
Sent | 10 Feb 2025, 0:24:30 UTC |
Report deadline | 18 Feb 2025, 0:24:30 UTC |
Received | 10 Feb 2025, 2:36:06 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Compute error |
Exit status | 1 (0x00000001) Unknown error code |
Computer ID | 10868879 |
Run time | 12 sec |
CPU time | |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 27.60 GFLOPS |
Application version | ATLAS Simulation v3.01 (vbox64_mt_mcore_atlas) x86_64-pc-linux-gnu |
Peak working set size | 3.25 MB |
Peak swap size | 5.05 MB |
Peak disk usage | 323.48 MB |
<core_client_version>7.18.1</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2025-02-10 01:52:40 (185592): Detected: vboxwrapper 26206 2025-02-10 01:52:40 (185592): Detected: BOINC client v7.18.1 2025-02-10 01:52:45 (185592): 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-02-10 01:52:45 (185592): Detected: VirtualBox VboxManage Interface (Version: 6.1.50) 2025-02-10 01:52:51 (185592): 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-02-10 01:52:51 (185592): WARNING: Communication with VM Hypervisor failed. 2025-02-10 01:52:51 (185592): ERROR: VBoxManage list hostinfo failed 01:52:51 (185592): called boinc_finish(1) </stderr_txt> ]]>
©2025 CERN