Name CMS_538776_1740518235.160186_0
Workunit 230560166
Created 25 Feb 2025, 21:17:17 UTC
Sent 25 Feb 2025, 21:53:20 UTC
Report deadline 28 Mar 2025, 21:53:20 UTC
Received 25 Feb 2025, 23:15:19 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 10567204
Run time 12 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 22.13 GFLOPS
Application version CMS Simulation v70.60 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.56 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-26 00:13:30 (1813120): vboxwrapper version 26208
2025-02-26 00:13:30 (1813120): BOINC client version: 7.18.1
2025-02-26 00:13:35 (1813120): 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-26 00:13:35 (1813120): Detected: VirtualBox VboxManage Interface (Version: 6.1.50)
2025-02-26 00:13:40 (1813120): 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-26 00:13:40 (1813120): WARNING: Communication with VM Hypervisor failed.
2025-02-26 00:13:40 (1813120): ERROR: VBoxManage list hostinfo failed
2025-02-26 00:13:40 (1813120): called boinc_finish(1)

</stderr_txt>
]]>


©2025 CERN