Name CMS_158402_1740373232.890044_0
Workunit 230533455
Created 24 Feb 2025, 5:00:34 UTC
Sent 24 Feb 2025, 6:50:40 UTC
Report deadline 27 Mar 2025, 6:50:40 UTC
Received 24 Feb 2025, 14:01:19 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 10870338
Run time 12 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 35.60 GFLOPS
Application version CMS Simulation v70.60 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.38 MB
Peak swap size 5.34 MB
Peak disk usage 1.23 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-02-23 23:42:06 (1375940): vboxwrapper version 26208
2025-02-23 23:42:06 (1375940): BOINC client version: 7.18.1
2025-02-23 23:42:11 (1375940): 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-02-23 23:42:11 (1375940): Detected: VirtualBox VboxManage Interface (Version: 6.1.50)
2025-02-23 23:42:17 (1375940): 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-02-23 23:42:17 (1375940): WARNING: Communication with VM Hypervisor failed.
2025-02-23 23:42:17 (1375940): ERROR: VBoxManage list hostinfo failed
2025-02-23 23:42:17 (1375940): called boinc_finish(1)

</stderr_txt>
]]>


©2025 CERN