Name | CMS_1587233_1672081225.060593_0 |
Workunit | 2266884 |
Created | 26 Dec 2022, 19:00:27 UTC |
Sent | 29 Dec 2022, 15:16:39 UTC |
Report deadline | 5 Jan 2023, 15:16:39 UTC |
Received | 29 Dec 2022, 16:22:25 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Compute error |
Exit status | 1 (0x00000001) Unknown error code |
Computer ID | 4684 |
Run time | 12 sec |
CPU time | 0 sec |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 7.30 GFLOPS |
Application version | CMS Simulation v60.70 (vbox64_mt_mcore_cms) x86_64-pc-linux-gnu |
Peak working set size | 3.34 MB |
Peak swap size | 4.91 MB |
Peak disk usage | 14.87 KB |
<core_client_version>7.20.2</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2022-12-29 11:20:45 (1316326): Detected: vboxwrapper 26206 2022-12-29 11:20:45 (1316326): Detected: BOINC client v7.20.2 2022-12-29 11:20:51 (1316326): 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. 2022-12-29 11:20:51 (1316326): Detected: VirtualBox VboxManage Interface (Version: 6.1.38) 2022-12-29 11:20:56 (1316326): 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. 2022-12-29 11:20:56 (1316326): WARNING: Communication with VM Hypervisor failed. 2022-12-29 11:20:56 (1316326): ERROR: VBoxManage list hostinfo failed 11:20:56 (1316326): called boinc_finish(1) </stderr_txt> ]]>
©2024 CERN