LHC@home

I just tried running a task with 6 cores on my system while putting a few of the other projects on pause.

It just blew up and disappeared after 546 seconds.

It seems my system can only run1 task at 4 cores and nothing more.

You guys said in the other thread it was 6600mb for one task and 4 cores.
So 6 cores will not be that much higher.

I also had BOINC trying to run 2 tasks at the same time and then 3.
This did not go well.

So what is going on? I am also considering putting a modified app_config back to get a work queue but allow it to run only 1 task with no memory limits. Any thoughts on this?

I almost got this dialed in, I am just trying to understand why it blew up with 6 cores and why even with plenty of memory left 2 tasks running at the same time blew up with only 4 cores per task.

It seems like the web settings don't allow for a work queue to be built up. Just the number of tasks at one time and the number of cores.

Lots of your tasks show this:

2021-05-07 21:16:20 (18364): VM is no longer is a running state. It is in 'GuruMeditation'.
2021-05-07 21:16:20 (18364): VM state change detected. (old = 'Running', new = 'GuruMeditation')

This is a severe VirtualBox error.

If this is caused by a corrupt ATLAS vdi you will have to reset the project and manually clean the slots directory.
It this is caused by a corrupt VirtualBox installation you will have to reinstall VirtualBox.

You do a good work to go thru Yeti's Checklist and work it up step by step:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4161&postid=29359#29359

Lots of your tasks show this:

2021-05-07 21:16:20 (18364): VM is no longer is a running state. It is in 'GuruMeditation'.
2021-05-07 21:16:20 (18364): VM state change detected. (old = 'Running', new = 'GuruMeditation')

This is a severe VirtualBox error.

If this is caused by a corrupt ATLAS vdi you will have to reset the project and manually clean the slots directory.
It this is caused by a corrupt VirtualBox installation you will have to reinstall VirtualBox.

well dang, I just had installed VirtualBox clean. I used an uninstaller program to get rid of .18 and did a clean install of .22

I have been getting lots of these guru errors as you saw, but I could never find any information on them.
I will do the exact same thing again, I will use an unistaller and download a fresh copy of VBox and try again.

That's done, but I need to clear out a back log of other projects first.
Keep an eye out here over the weekend for an update and thanks for your replies on all my threads.

You do a good work to go thru Yeti's Checklist and work it up step by step:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4161&postid=29359#29359

This problem is not explained in the checklist. That is for setup of Vbox and the virtual environment on your system. This problem is deeper than that as you see by the other reply.