Name CMS_2036909_1703683042.829419_0
Workunit 2372341
Created 27 Dec 2023, 13:17:25 UTC
Sent 29 Dec 2023, 5:15:02 UTC
Report deadline 5 Jan 2024, 5:15:02 UTC
Received 29 Dec 2023, 6:32:18 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 5061
Run time 12 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 6.43 GFLOPS
Application version CMS Simulation v60.70 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.38 MB
Peak swap size 5.29 MB
Peak disk usage 15.29 KB

Stderr output

<core_client_version>7.20.5</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2023-12-28 23:30:14 (3304): Detected: vboxwrapper 26206
2023-12-28 23:30:14 (3304): Detected: BOINC client v7.20.5
2023-12-28 23:30:19 (3304): 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-12-28 23:30:19 (3304): Detected: VirtualBox VboxManage Interface (Version: 6.1.38)
2023-12-28 23:30:25 (3304): 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-12-28 23:30:25 (3304): WARNING: Communication with VM Hypervisor failed.
2023-12-28 23:30:25 (3304): ERROR: VBoxManage list hostinfo failed
23:30:25 (3304): called boinc_finish(1)

</stderr_txt>
]]>


©2024 CERN