Name CMS_660703_1671510832.844013_0
Workunit 2264924
Created 20 Dec 2022, 4:33:57 UTC
Sent 23 Dec 2022, 15:17:31 UTC
Report deadline 30 Dec 2022, 15:17:31 UTC
Received 23 Dec 2022, 15:58:56 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 4684
Run time 12 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 7.30 GFLOPS
Application version CMS Simulation v60.70 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.36 MB
Peak swap size 4.91 MB
Peak disk usage 14.86 KB

Stderr output

<core_client_version>7.20.2</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2022-12-23 10:52:27 (588412): Detected: vboxwrapper 26206
2022-12-23 10:52:27 (588412): Detected: BOINC client v7.20.2
2022-12-23 10:52:32 (588412): Error in guest additions for VM: -1041038848
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.

2022-12-23 10:52:32 (588412): Detected: VirtualBox VboxManage Interface (Version: 6.1.38)
2022-12-23 10:52:38 (588412): Error in host info for VM: -1041038848
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.

2022-12-23 10:52:38 (588412): WARNING: Communication with VM Hypervisor failed.
2022-12-23 10:52:38 (588412): ERROR: VBoxManage list hostinfo failed
10:52:38 (588412): called boinc_finish(1)

</stderr_txt>
]]>


©2024 CERN