Name | CMS_3361054_1747844226.232865_0 |
Workunit | 232474521 |
Created | 21 May 2025, 16:17:09 UTC |
Sent | 21 May 2025, 16:55:47 UTC |
Report deadline | 21 Jun 2025, 16:55:47 UTC |
Received | 21 May 2025, 16:57:51 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Compute error |
Exit status | 1 (0x00000001) Unknown error code |
Computer ID | 10806306 |
Run time | 12 sec |
CPU time | |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 21.82 GFLOPS |
Application version | CMS Simulation v70.91 (vbox64_mt_mcore_cms) x86_64-pc-linux-gnu |
Peak working set size | 3.62 MB |
Peak swap size | 5.40 MB |
Peak disk usage | 1.28 MB |
<core_client_version>7.18.1</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2025-05-21 18:56:09 (39065): vboxwrapper version 26210 2025-05-21 18:56:09 (39065): BOINC client version: 7.18.1 2025-05-21 18:56:14 (39065): 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-05-21 18:56:14 (39065): Detected: VirtualBox VboxManage Interface (Version: 6.1.50) 2025-05-21 18:56:19 (39065): 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-05-21 18:56:19 (39065): WARNING: Communication with VM Hypervisor failed. 2025-05-21 18:56:19 (39065): ERROR: VBoxManage list hostinfo failed 2025-05-21 18:56:19 (39065): called boinc_finish(1) </stderr_txt> ]]>
©2025 CERN