Name CMS_2745892_1749001054.258147_0
Workunit 232840268
Created 4 Jun 2025, 1:37:37 UTC
Sent 4 Jun 2025, 2:21:03 UTC
Report deadline 5 Jul 2025, 2:21:03 UTC
Received 4 Jun 2025, 2:22:36 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 10803660
Run time 12 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.61 MB
Peak swap size 5.64 MB
Peak disk usage 1.28 MB

Stderr output

<core_client_version>7.20.2</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2025-06-04 04:10:58 (7589): vboxwrapper version 26210
2025-06-04 04:10:58 (7589): BOINC client version: 7.20.2
2025-06-04 04:11:04 (7589): 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-04 04:11:04 (7589): Detected: VirtualBox VboxManage Interface (Version: 6.1.50)
2025-06-04 04:11:09 (7589): 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-04 04:11:09 (7589): WARNING: Communication with VM Hypervisor failed.
2025-06-04 04:11:09 (7589): ERROR: VBoxManage list hostinfo failed
2025-06-04 04:11:09 (7589): called boinc_finish(1)

</stderr_txt>
]]>


©2025 CERN