Name CMS_2138784_1682335791.770158_0
Workunit 2302007
Created 24 Apr 2023, 11:29:52 UTC
Sent 25 Apr 2023, 10:47:51 UTC
Report deadline 2 May 2023, 10:47:51 UTC
Received 25 Apr 2023, 10:52:36 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 4933
Run time 12 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 4.54 GFLOPS
Application version CMS Simulation v60.70 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.43 MB
Peak swap size 5.05 MB
Peak disk usage 17.96 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-04-25 04:50:37 (1333997): Detected: vboxwrapper 26206
2023-04-25 04:50:37 (1333997): Detected: BOINC client v7.18.1
2023-04-25 04:50:42 (1333997): 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-04-25 04:50:42 (1333997): Detected: VirtualBox VboxManage Interface (Version: 6.1.38)
2023-04-25 04:50:48 (1333997): 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-04-25 04:50:48 (1333997): WARNING: Communication with VM Hypervisor failed.
2023-04-25 04:50:48 (1333997): ERROR: VBoxManage list hostinfo failed
04:50:48 (1333997): called boinc_finish(1)

</stderr_txt>
]]>


©2024 CERN