Name | CMS_2768098_1728108231.238938_0 |
Workunit | 225849228 |
Created | 5 Oct 2024, 6:03:53 UTC |
Sent | 5 Oct 2024, 7:39:35 UTC |
Report deadline | 5 Nov 2024, 7:39:35 UTC |
Received | 5 Oct 2024, 7:41:13 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Compute error |
Exit status | 1 (0x00000001) Unknown error code |
Computer ID | 10853779 |
Run time | 12 sec |
CPU time | 0 sec |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 32.26 GFLOPS |
Application version | CMS Simulation v70.30 (vbox64_mt_mcore_cms) x86_64-pc-linux-gnu |
Peak working set size | 3.54 MB |
Peak swap size | 5.40 MB |
Peak disk usage | 17.72 KB |
<core_client_version>7.18.1</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2024-10-05 02:39:38 (178299): vboxwrapper version 26207 2024-10-05 02:39:38 (178299): BOINC client version: 7.18.1 2024-10-05 02:39:43 (178299): 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-10-05 02:39:43 (178299): Detected: VirtualBox VboxManage Interface (Version: 7.0.10) 2024-10-05 02:39:48 (178299): 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-10-05 02:39:48 (178299): WARNING: Communication with VM Hypervisor failed. 2024-10-05 02:39:48 (178299): ERROR: VBoxManage list hostinfo failed 2024-10-05 02:39:48 (178299): called boinc_finish(1) </stderr_txt> ]]>
©2024 CERN