Name CMS_268911_1700183605.948093_0
Workunit 2353212
Created 17 Nov 2023, 1:13:26 UTC
Sent 17 Nov 2023, 19:40:01 UTC
Report deadline 24 Nov 2023, 19:40:01 UTC
Received 17 Nov 2023, 19:44:42 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 4318
Run time 14 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 63.07 GFLOPS
Application version CMS Simulation v60.70 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.40 MB
Peak swap size 11.33 MB
Peak disk usage 15.12 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-11-17 19:42:58 (913163): Detected: vboxwrapper 26206
2023-11-17 19:42:58 (913163): Detected: BOINC client v7.18.1
2023-11-17 19:43:04 (913163): 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-11-17 19:43:04 (913163): Detected: VirtualBox VboxManage Interface (Version: 6.1.38)
2023-11-17 19:43:11 (913163): 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-11-17 19:43:11 (913163): WARNING: Communication with VM Hypervisor failed.
2023-11-17 19:43:11 (913163): ERROR: VBoxManage list hostinfo failed
19:43:11 (913163): called boinc_finish(1)

</stderr_txt>
]]>


©2024 CERN