Name | CMS_1979980_1748776235.217066_0 |
Workunit | 232750431 |
Created | 1 Jun 2025, 11:10:36 UTC |
Sent | 1 Jun 2025, 12:06:14 UTC |
Report deadline | 2 Jul 2025, 12:06:14 UTC |
Received | 1 Jun 2025, 12:08:18 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Compute error |
Exit status | 1 (0x00000001) Unknown error code |
Computer ID | 10803660 |
Run time | 14 sec |
CPU time | |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 21.40 GFLOPS |
Application version | CMS Simulation v70.91 (vbox64_mt_mcore_cms) x86_64-pc-linux-gnu |
Peak working set size | 3.59 MB |
Peak swap size | 15.94 MB |
Peak disk usage | 1.28 MB |
<core_client_version>7.20.2</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2025-06-01 13:56:10 (3404): vboxwrapper version 26210 2025-06-01 13:56:10 (3404): BOINC client version: 7.20.2 2025-06-01 13:56:17 (3404): Error in guest additions for VM: -182 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-01 13:56:17 (3404): Detected: VirtualBox VboxManage Interface (Version: 6.1.50) 2025-06-01 13:56:22 (3404): Error in host info for VM: -182 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-01 13:56:22 (3404): WARNING: Communication with VM Hypervisor failed. 2025-06-01 13:56:22 (3404): ERROR: VBoxManage list hostinfo failed 2025-06-01 13:56:22 (3404): called boinc_finish(1) </stderr_txt> ]]>
©2025 CERN