Message boards :
Number crunching :
Tasks Fail on Linux Host
Message board moderation
Author | Message |
---|---|
Send message Joined: 30 May 08 Posts: 93 Credit: 5,160,246 RAC: 0 |
I'm trying to get VBox tasks running on one of my Linux hosts that used to not have a problem running those tasks here. As a result of troubleshooting a hardware problem (bad RAM since removed), I wiped the HDD clean and re-installed the OS (Mint 18). I've installed VBox 5.1.22 and its extension pack, like my other hosts (including another Linux machine) which have run VBox tasks recently (though not LHC). The three Theory tasks I've run all failed after a short time and the stderr output includes errors like NS_ERROR_FAILURE and VBOX_E_OBJECT_NOT_FOUND. I'm hoping I'm just missing some setting I can't think of. Virtualization (SVM in my ASUS motherboard) is enabled in the BIOS. Maybe I have a corrupt installation; however, I've unistalled/re-installed VBox and the extension pack a couple of times, including rebooting between each uninstall and reinstall. So, if that's it, I'm not sure how I would correct it. |
Send message Joined: 20 Jun 14 Posts: 372 Credit: 238,712 RAC: 0 |
Is the user running boinc a member of the vbox group? |
Send message Joined: 30 May 08 Posts: 93 Credit: 5,160,246 RAC: 0 |
Is the user running boinc a member of the vbox group? "boinc" is the user running BOINC, correct? If so, it seems that it's not in the vbox group:
boinc : boinc video mark@FrankenLinux ~ $
|
Send message Joined: 22 Mar 17 Posts: 55 Credit: 10,223,976 RAC: 2,477 |
Was BOINC restarted after the VBox installation. I think it's detected at BOINC startup like hardware. There should be a line in the event log saying it found VBox. |
Send message Joined: 30 May 08 Posts: 93 Credit: 5,160,246 RAC: 0 |
...There should be a line in the event log saying it found VBox. From the event log following a recent startup: Fri 23 Jun 2017 10:40:35 PM EDT | | VirtualBox version: 5.1.22r115126 |
Send message Joined: 30 May 08 Posts: 93 Credit: 5,160,246 RAC: 0 |
Based on the exit code of some of my tasks at another project, a forum poster there suggested my BOINC install might have a permission problem. After going through a couple of uninstall/reinstall cycles, I'm back in business (who knows why it took more than one). Problem solved... Thanks for the feedback. |
©2024 CERN