| Name | CMS_3627366_1744838115.722581_0 |
| Workunit | 231665220 |
| Created | 16 Apr 2025, 21:15:19 UTC |
| Sent | 16 Apr 2025, 21:58:26 UTC |
| Report deadline | 17 May 2025, 21:58:26 UTC |
| Received | 17 Apr 2025, 21:55:37 UTC |
| Server state | Over |
| Outcome | Computation error |
| Client state | Compute error |
| Exit status | 1 (0x00000001) Unknown error code |
| Computer ID | 10831573 |
| Run time | 12 sec |
| CPU time | |
| Validate state | Invalid |
| Credit | 0.00 |
| Device peak FLOPS | 25.08 GFLOPS |
| Application version | CMS Simulation v70.91 (vbox64_mt_mcore_cms) x86_64-pc-linux-gnu |
| Peak working set size | 3.50 MB |
| Peak swap size | 5.40 MB |
| Peak disk usage | 1.28 MB |
Stderr output
<core_client_version>7.18.1</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2025-04-17 16:45:38 (4019): vboxwrapper version 26210 2025-04-17 16:45:38 (4019): BOINC client version: 7.18.1 2025-04-17 16:45:43 (4019): 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-04-17 16:45:43 (4019): Detected: VirtualBox VboxManage Interface (Version: 7.0.26) 2025-04-17 16:45:48 (4019): 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-04-17 16:45:48 (4019): WARNING: Communication with VM Hypervisor failed. 2025-04-17 16:45:48 (4019): ERROR: VBoxManage list hostinfo failed 2025-04-17 16:45:48 (4019): called boinc_finish(1) </stderr_txt> ]]>
©2025 CERN