| Name | CMS_1992353_1736016897.849479_0 |
| Workunit | 229673678 |
| Created | 4 Jan 2025, 18:55:01 UTC |
| Sent | 4 Jan 2025, 19:19:39 UTC |
| Report deadline | 4 Feb 2025, 19:19:39 UTC |
| Received | 4 Jan 2025, 19:23:11 UTC |
| Server state | Over |
| Outcome | Computation error |
| Client state | Compute error |
| Exit status | 1 (0x00000001) Unknown error code |
| Computer ID | 10850388 |
| Run time | 12 sec |
| CPU time | 0 sec |
| Validate state | Invalid |
| Credit | 0.00 |
| Device peak FLOPS | 30.78 GFLOPS |
| Application version | CMS Simulation v70.30 (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 | 17.93 KB |
Stderr output
<core_client_version>7.18.1</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2025-01-04 14:21:26 (10022): vboxwrapper version 26207 2025-01-04 14:21:26 (10022): BOINC client version: 7.18.1 2025-01-04 14:21:31 (10022): 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-01-04 14:21:31 (10022): Detected: VirtualBox VboxManage Interface (Version: 6.1.50) 2025-01-04 14:21:36 (10022): 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-01-04 14:21:36 (10022): WARNING: Communication with VM Hypervisor failed. 2025-01-04 14:21:36 (10022): ERROR: VBoxManage list hostinfo failed 2025-01-04 14:21:36 (10022): called boinc_finish(1) </stderr_txt> ]]>
©2025 CERN