Name CMS_586746_1748316443.813950_0
Workunit 232630685
Created 27 May 2025, 3:27:25 UTC
Sent 27 May 2025, 4:29:55 UTC
Report deadline 27 Jun 2025, 4:29:55 UTC
Received 28 May 2025, 4:40:01 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 10875614
Run time 12 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 35.84 GFLOPS
Application version CMS Simulation v70.91 (vbox64_mt_mcore_cms)
x86_64-pc-linux-gnu
Peak working set size 3.61 MB
Peak swap size 5.40 MB
Peak disk usage 1.28 MB

Stderr output

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2025-05-27 06:36:59 (3412321): vboxwrapper version 26210
2025-05-27 06:36:59 (3412321): BOINC client version: 7.18.1
2025-05-27 06:37:04 (3412321): 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-05-27 06:37:04 (3412321): Detected: VirtualBox VboxManage Interface (Version: 7.0.20)
2025-05-27 06:37:09 (3412321): 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-05-27 06:37:09 (3412321): WARNING: Communication with VM Hypervisor failed.
2025-05-27 06:37:09 (3412321): ERROR: VBoxManage list hostinfo failed
2025-05-27 06:37:09 (3412321): called boinc_finish(1)

</stderr_txt>
]]>


©2025 CERN