Name CMS_1963585_1658568423.700882_0
Workunit 2198330
Created 23 Jul 2022, 9:27:04 UTC
Sent 26 Jul 2022, 8:34:19 UTC
Report deadline 2 Aug 2022, 8:34:19 UTC
Received 26 Jul 2022, 8:43:44 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 4601
Run time 12 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 3.53 GFLOPS
Application version CMS Simulation v60.63 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.68 MB
Peak swap size 5.48 MB
Peak disk usage 15.16 KB

Stderr output

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2022-07-26 10:41:59 (5382): Detected: vboxwrapper 26205
2022-07-26 10:41:59 (5382): Detected: BOINC client v7.18.1
2022-07-26 10:42:04 (5382): 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.

2022-07-26 10:42:04 (5382): Detected: VirtualBox VboxManage Interface (Version: 6.1.34)
2022-07-26 10:42:10 (5382): 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.

2022-07-26 10:42:10 (5382): WARNING: Communication with VM Hypervisor failed.
2022-07-26 10:42:10 (5382): ERROR: VBoxManage list hostinfo failed
10:42:10 (5382): called boinc_finish(1)

</stderr_txt>
]]>


©2024 CERN