Name | 08370619_13_0 |
Workunit | 8201272 |
Created | 12 Jun 2021, 23:41:25 UTC |
Sent | 13 Jun 2021, 2:13:49 UTC |
Report deadline | 18 Jun 2021, 2:13:49 UTC |
Received | 13 Jun 2021, 2:24:19 UTC |
Server state | Over |
Outcome | Computation error |
Client state | Aborted by user |
Exit status | 203 (0x000000CB) EXIT_ABORTED_VIA_GUI |
Computer ID | 12041 |
Run time | 16 sec |
CPU time | |
Validate state | Invalid |
Credit | 0.00 |
Device peak FLOPS | 3.70 GFLOPS |
Application version | boinc2docker v1.14 (vbox64_mt) x86_64-pc-linux-gnu |
Peak working set size | 3.35 MB |
Peak swap size | 28.17 MB |
Peak disk usage | 600.52 MB |
<core_client_version>7.16.16</core_client_version> <![CDATA[ <message> aborted by user</message> <stderr_txt> 2021-06-13 04:15:39 (7468): vboxwrapper (7.7.26197): starting 2021-06-13 04:15:50 (7468): Error in guest additions for VM: -1041038848 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. 2021-06-13 04:15:50 (7468): Feature: Checkpoint interval offset (216 seconds) 2021-06-13 04:15:50 (7468): Detected: VirtualBox VboxManage Interface (Version: 5.2.42) 2021-06-13 04:15:55 (7468): Error in host info for VM: -1041038848 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. 2021-06-13 04:15:55 (7468): WARNING: Communication with VM Hypervisor failed. 2021-06-13 04:15:55 (7468): Could not communicate with VM Hypervisor. Rescheduling execution for a later date. </stderr_txt> ]]>
©2024 COPYRIGHT 2017-2018 NCN