WU are faiiing after reboot


Advanced search

Message boards : Number crunching : WU are faiiing after reboot

Author Message
RaimundD
Send message
Joined: 9 Jan 16
Posts: 5
Credit: 195,906
RAC: 0
    
Message 5753 - Posted: 3 Dec 2016, 8:04:42 UTC

Hi,

currently I see frequently that WU are failing after a reboot. The multi core units seem to be more stable but the single core fail close to 100%.

Does anyone see this behavior also? Is there something I can do?

Thanx
Raimund

computezrmle
Send message
Joined: 29 Oct 14
Posts: 54
Credit: 1,137,404
RAC: 0
    
Message 5754 - Posted: 3 Dec 2016, 8:26:18 UTC - in response to Message 5753.
Last modified: 3 Dec 2016, 8:35:10 UTC

It looks like a problem regarding your VirtualBox installation.

WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.

You should check/reinstall VirtualBox and restart your host.

Edit: you may test your installation with another project, e.g. LHC Theory, since ATLAS causes other problems at the moment.

RaimundD
Send message
Joined: 9 Jan 16
Posts: 5
Credit: 195,906
RAC: 0
    
Message 5766 - Posted: 4 Dec 2016, 7:36:06 UTC - in response to Message 5754.

Hi,

I saw this message also. But some WU work others not. I will try another project.

Regards
Raimund

RaimundD
Send message
Joined: 9 Jan 16
Posts: 5
Credit: 195,906
RAC: 0
    
Message 5815 - Posted: 12 Dec 2016, 19:49:40 UTC - in response to Message 5766.

Hi,

I still have quite a lot failures. Tried other projects, not really more stable. Re-installed virtualbox, no improvement.

Any more suggestions?

Thanx
Raimund

PHILIPPE
Send message
Joined: 24 Jul 16
Posts: 84
Credit: 53,413
RAC: 0
    
Message 5816 - Posted: 12 Dec 2016, 20:27:53 UTC - in response to Message 5815.
Last modified: 12 Dec 2016, 21:00:19 UTC

Hi , RaimundD,

I don't have Linux but reading your log :

2016-12-12 18:41:08 (1929):
Command: VBoxManage -q startvm "boinc_0689674a581a2d08" --type headless
Exit Code: 1
Output:
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.
VBoxManage: error: The virtual machine 'boinc_0689674a581a2d08' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
Waiting for VM "boinc_0689674a581a2d08" to power on...


A search on the ubuntuforum gives a possible solution for your trouble
See this page

Re: Virtual box error NS_ERROR_FAILURE (0x80004005)

Same thing happened to me after installing some updates. I checked and DKMS was already installed.

But running the command prefaced by sudo fixed everything.

Code:

sudo /etc/init.d/vboxdrv setup

----------------------------------------------------------------------------------------------------------------------------------------------------------------
Or It seems that the session user must have root rights to do correct pack install:
with debian
adduser guest sudo
following the advice of this page (in french at the bottom of the page)
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Adapt it to your configuration,maybe it will help you...

RaimundD
Send message
Joined: 9 Jan 16
Posts: 5
Credit: 195,906
RAC: 0
    
Message 5829 - Posted: 15 Dec 2016, 21:10:18 UTC - in response to Message 5816.

Hi,

I tried a lot of things, including reinstalling virtualbox. Still no success:-(

Anyway, will try again.

Raimund

RaimundD
Send message
Joined: 9 Jan 16
Posts: 5
Credit: 195,906
RAC: 0
    
Message 5833 - Posted: 17 Dec 2016, 8:23:42 UTC - in response to Message 5829.

Hi,

I solved it finally.
It seems the startup time of my computer is to small;-) I started boinc in script which is launched at login. As I do a automatic login after boot the device /dev/vboxdrv was not ready yet and lead to failed WUs.
Just delaying the launch solved the problem.

Raimund

Message boards : Number crunching : WU are faiiing after reboot