Name CMS_3756603_1685763973.306641_0
Workunit 2310183
Created 3 Jun 2023, 3:46:18 UTC
Sent 6 Jun 2023, 19:57:24 UTC
Report deadline 13 Jun 2023, 19:57:24 UTC
Received 7 Jun 2023, 1:23:12 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 1700
Run time 13 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 4.25 GFLOPS
Application version CMS Simulation v60.70 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.37 MB
Peak swap size 5.29 MB
Peak disk usage 15.06 KB

Stderr output

<core_client_version>7.16.16</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2023-06-06 20:21:44 (100658): Detected: vboxwrapper 26206
2023-06-06 20:21:44 (100658): Detected: BOINC client v7.16.16
2023-06-06 20:21:49 (100658): 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-06-06 20:21:49 (100658): Detected: VirtualBox VboxManage Interface (Version: 6.1.38)
2023-06-06 20:21:55 (100658): 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-06-06 20:21:55 (100658): WARNING: Communication with VM Hypervisor failed.
2023-06-06 20:21:55 (100658): ERROR: VBoxManage list hostinfo failed
20:21:55 (100658): called boinc_finish(1)

</stderr_txt>
]]>


©2024 CERN