Name CMS_3310027_1715669426.915120_0
Workunit 2414045
Created 14 May 2024, 6:50:27 UTC
Sent 14 May 2024, 17:18:18 UTC
Report deadline 21 May 2024, 17:18:18 UTC
Received 14 May 2024, 17:58:15 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 4418
Run time 13 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 5.39 GFLOPS
Application version CMS Simulation v61.01 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.56 MB
Peak swap size 5.40 MB
Peak disk usage 3.81 MB

Stderr output

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2024-05-15 02:56:20 (8599): vboxwrapper version 26207
2024-05-15 02:56:20 (8599): BOINC client version: 7.18.1
2024-05-15 02:56:26 (8599): Error in guest additions for VM: -182
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.

2024-05-15 02:56:26 (8599): Detected: VirtualBox VboxManage Interface (Version: 6.1.50)
2024-05-15 02:56:32 (8599): Error in host info for VM: -182
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.

2024-05-15 02:56:32 (8599): WARNING: Communication with VM Hypervisor failed.
2024-05-15 02:56:32 (8599): ERROR: VBoxManage list hostinfo failed
2024-05-15 02:56:32 (8599): called boinc_finish(1)

</stderr_txt>
]]>


©2024 CERN