Message boards : ATLAS application : Atlas virtuabox errors
Message board moderation

To post messages, you must log in.

AuthorMessage
Guiri-One[Andalucia]

Send message
Joined: 1 Feb 06
Posts: 66
Credit: 9,723
RAC: 0
Message 37918 - Posted: 4 Feb 2019, 15:28:13 UTC
Last modified: 4 Feb 2019, 15:28:28 UTC

Hi team,

I sometimes (??) have issues with Atles (and theory) tasks.

Example:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=214905801

Why this one didn't work? I got no clue what to do to make my laptop useful but is getting hard for LHC...

Thx¡
Javi
ID: 37918 · Report as offensive     Reply Quote
Crystal Pellet
Volunteer moderator
Volunteer tester

Send message
Joined: 14 Jan 10
Posts: 1094
Credit: 6,832,217
RAC: 688
Message 37919 - Posted: 4 Feb 2019, 15:41:21 UTC - in response to Message 37918.  

It seems this task had several days off and then it resumed again.
After the restart VirtualBox did net get enough memory.

2019-01-30 15:59:50 (4824): Stopping VM.
2019-01-30 16:00:21 (4824): Successfully stopped VM.
2019-02-04 14:33:32 (9476): vboxwrapper (7.7.26196): starting
2019-02-04 14:33:33 (9476): Feature: Checkpoint interval offset (8 seconds)
2019-02-04 14:33:33 (9476): Detected: VirtualBox VboxManage Interface (Version: 6.0.0)
2019-02-04 14:33:33 (9476): Detected: Minimum checkpoint interval (900.000000 seconds)
2019-02-04 14:33:34 (9476): Starting VM. (boinc_107667830f4b2f63, slot#1)
2019-02-04 14:34:14 (9476): Error in start VM for VM: -2147467259
Command:
VBoxManage -q startvm "boinc_107667830f4b2f63" --type headless
Output:
Waiting for VM "boinc_107667830f4b2f63" to power on...
VBoxManage.exe: error: Failed to load unit 'pgm' (VERR_EM_NO_MEMORY)
ID: 37919 · Report as offensive     Reply Quote
Guiri-One[Andalucia]

Send message
Joined: 1 Feb 06
Posts: 66
Credit: 9,723
RAC: 0
Message 37929 - Posted: 5 Feb 2019, 11:04:27 UTC - in response to Message 37919.  

Being "old" or unable to open a session in that moment should not be a reason to send to the waste bien hours of CPU work...
ID: 37929 · Report as offensive     Reply Quote
bronco

Send message
Joined: 13 Apr 18
Posts: 443
Credit: 8,438,885
RAC: 0
Message 37931 - Posted: 5 Feb 2019, 12:06:07 UTC - in response to Message 37929.  

Being "old" or unable to open a session in that moment should not be a reason to send to the waste bien hours of CPU work...


What should they do? Remember... if the VM fails then there exists no useful result to send to the server, to the waste bin or anywhere else.
ID: 37931 · Report as offensive     Reply Quote
Guiri-One[Andalucia]

Send message
Joined: 1 Feb 06
Posts: 66
Credit: 9,723
RAC: 0
Message 37932 - Posted: 5 Feb 2019, 14:17:28 UTC - in response to Message 37931.  

Maybe try to open the VM couple of times before assuming is not there (which was not true) and send everything to hell.
When usual Boinc tasks can't connect to internet, they are not directly waste. Boinc tries later...
ID: 37932 · Report as offensive     Reply Quote
bronco

Send message
Joined: 13 Apr 18
Posts: 443
Credit: 8,438,885
RAC: 0
Message 37942 - Posted: 6 Feb 2019, 8:37:19 UTC - in response to Message 37932.  

Maybe try to open the VM couple of times before assuming is not there (which was not true) and send everything to hell.
When usual Boinc tasks can't connect to internet, they are not directly waste. Boinc tries later...


If BOINC has a task then it can safely assume there was at one time an Internet connection and that if there isn't a connection at the moment then there likely will be one sooner or later. It's makes sense to keep on trying in those circumstances.

The log doesn't say the VM wasn't there. It says VboxManage could not find it which suggests to me the pointer to the file got corrupted. If VboxManage cannot find the file then there is no other option but to declare the task complete. What else can it do? Should it sniff around your disk until it finds something it can start and hope it's the VM it's looking for?
ID: 37942 · Report as offensive     Reply Quote

Message boards : ATLAS application : Atlas virtuabox errors


©2022 CERN