Name CMS_3337688_1678357499.097793_0
Workunit 2285353
Created 9 Mar 2023, 10:25:04 UTC
Sent 11 Mar 2023, 6:32:18 UTC
Report deadline 18 Mar 2023, 6:32:18 UTC
Received 11 Mar 2023, 7:00:06 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 4933
Run time 11 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 4.48 GFLOPS
Application version CMS Simulation v60.70 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.30 MB
Peak swap size 5.05 MB
Peak disk usage 17.85 KB

Stderr output

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2023-03-10 23:58:27 (100610): Detected: vboxwrapper 26206
2023-03-10 23:58:27 (100610): Detected: BOINC client v7.18.1
2023-03-10 23:58:32 (100610): 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.

2023-03-10 23:58:32 (100610): Detected: VirtualBox VboxManage Interface (Version: 6.1.38)
2023-03-10 23:58:38 (100610): 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.

2023-03-10 23:58:38 (100610): WARNING: Communication with VM Hypervisor failed.
2023-03-10 23:58:38 (100610): ERROR: VBoxManage list hostinfo failed
23:58:38 (100610): called boinc_finish(1)

</stderr_txt>
]]>


©2024 CERN