Name CMS_2460174_1736186264.043544_0
Workunit 229699197
Created 6 Jan 2025, 17:57:45 UTC
Sent 6 Jan 2025, 18:15:58 UTC
Report deadline 6 Feb 2025, 18:15:58 UTC
Received 6 Jan 2025, 18:19:07 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 10850388
Run time 13 sec
CPU time 0 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 30.78 GFLOPS
Application version CMS Simulation v70.30 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 14.07 MB
Peak swap size 74.09 MB
Peak disk usage 17.94 KB

Stderr output

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2025-01-06 13:17:07 (1718043): vboxwrapper version 26207
2025-01-06 13:17:07 (1718043): BOINC client version: 7.18.1
2025-01-06 13:17:13 (1718043): 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.

2025-01-06 13:17:13 (1718043): Detected: VirtualBox VboxManage Interface (Version: 6.1.50)
2025-01-06 13:17:19 (1718043): 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.

2025-01-06 13:17:19 (1718043): WARNING: Communication with VM Hypervisor failed.
2025-01-06 13:17:19 (1718043): ERROR: VBoxManage list hostinfo failed
2025-01-06 13:17:19 (1718043): called boinc_finish(1)

</stderr_txt>
]]>


©2025 CERN