Name | Theory_2848-4458253-602_2 |
Workunit | 231626883 |
Created | 16 Apr 2025, 23:33:37 UTC |
Sent | 17 Apr 2025, 9:15:09 UTC |
Report deadline | 28 Apr 2025, 9:15:09 UTC |
Received | 17 Apr 2025, 13:22:06 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Compute error |
Exit status | 1 (0x00000001) Unknown error code |
Computer ID | 10803211 |
Run time | 14 sec |
CPU time | |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 6.03 GFLOPS |
Application version | Theory Simulation v300.95 (vbox64_theory) x86_64-pc-linux-gnu |
Peak working set size | 3.49 MB |
Peak swap size | 5.47 MB |
Peak disk usage | 1.62 MB |
<core_client_version>7.16.16</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255)</message> <stderr_txt> 2025-04-17 10:24:26 (278621): vboxwrapper version 26210 2025-04-17 10:24:26 (278621): BOINC client version: 7.16.16 2025-04-17 10:24:32 (278621): 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-04-17 10:24:32 (278621): Detected: VirtualBox VboxManage Interface (Version: 7.0.12) 2025-04-17 10:24:38 (278621): 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-04-17 10:24:38 (278621): WARNING: Communication with VM Hypervisor failed. 2025-04-17 10:24:38 (278621): ERROR: VBoxManage list hostinfo failed 2025-04-17 10:24:38 (278621): called boinc_finish(1) </stderr_txt> ]]>
©2025 CERN