[quote]Same error as [url]https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6248

Much disappointing. And a bit surprising, to me, since we're speaking of the CERN.
However I don't know how much useful can actually be the work processed on our PCs, and so how much effort it deserves beside CERN "regular" work.

It's a matter of fact that, among the few distributed computing projects still alive (a small fraction of those running not so many years ago), this one looks more prone to periodical issues (in my limited experience, at least), which I find... unexpected.
--
Bye, Lem

I think this is due to the extra shuffling the OS has to do it make the tasks a little slower each time

well, I would understand "a little slower" - but in this case the difference is tremendous.
Why would I waste 3 cores per task if I can achieve the same computation result with 2 cores?
It I were not limited with 32GB RAM, I would now try eight 1-core tasks in order to find out how this relates to the 2-core and 3-core operation.

For me on one computer resetting the project does not fix the problems, I will monitor further.

I did like Crystal did and removed the project and then attached to it again and the problem was solved.

They could have announced it on the forum and leave the decision to abort to the crunchers. They could also have tested them on the dev-site first. But it is what it is, there's no point in crying over spilled milk.

I wasn't aware Boinc had the facility to remotely abort a started task. Perhaps it's just other projects don't like doing so. I'm not sure why anyone would want to finish a task which is just going to be discarded at the project end.

... Ivan isn't the only one running CMS ...

however, it looks like, doesn't it ?

Same error as described here:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5982&postid=47976
Same solution, except that here (so far only!) the ATLAS vdi is affected.

4/25/2023 8:15:20 PM | LHC@home | Sending scheduler request: To fetch work.
4/25/2023 8:15:20 PM | LHC@home | Requesting new tasks for CPU
4/25/2023 8:15:21 PM | LHC@home | Scheduler request completed: got 0 new tasks
4/25/2023 8:15:21 PM | LHC@home | No tasks sent
4/25/2023 8:15:21 PM | LHC@home | No tasks are available for ATLAS Simulation

2023-04-24 10:34:15 (19704): Adding virtual disk drive to VM. (ATLAS_vbox_3.01_image.vdi)
2023-04-24 10:34:22 (19704): Error in deregister parent vdi for VM: -2135228404
Command:
VBoxManage -q closemedium "C:\ProgramData\BOINC/projects/lhcathome.cern.ch_lhcathome/ATLAS_vbox_3.01_image.vdi"
Output:
VBoxManage.exe: error: Cannot close medium 'C:\ProgramData\BOINC\projects\lhcathome.cern.ch_lhcathome\ATLAS_vbox_3.01_image.vdi' because it has 1 child media
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: "Close()" at line 1875 of file VBoxManageDisk.cpp

2023-04-24 10:34:22 (19704): Could not create VM
2023-04-24 10:34:22 (19704): ERROR: VM failed to start
2023-04-24 10:34:22 (19704): Powering off VM.
2023-04-24 10:34:22 (19704): Deregistering VM. (boinc_59cce48668c5a14b, slot#0)
2023-04-24 10:34:23 (19704): Removing network bandwidth throttle group from VM.
2023-04-24 10:34:23 (19704): Removing VM from VirtualBox.

I can confirm we are now mostly running the Run 3 tasks. I asked for some test tasks here and got more than I thought :)

These tasks are processing 500 events but each event is faster than before so the overall run time should be only a little bit longer.

Also as you have noticed the console monitoring doesn’t work due to changes in the logging format. The “top” monitoring on Alt-F3 also shows a single python process instead of multiple athena.py processes.

Is the VM RAM size going to be adjusted eventually or will the current defaults be used because 3.01 can run 'Run 2' and 'Run 3'? Will the VM change the RAM assigned by 'Run 2' vs 'Run 3'?

The RAM size is set to 4000 MB independend of running tasks from run 2 or run 3.
It also doesn't matter whether you run single core vbox tasks or multi-core e.g. 4 or 8 cores.

The tasks that we crunch here are not results produced by LHC but simulations. So we are not depending on LHC running or not.

Be that as it may, I rather suspect what we crunch here is based on experimental reality. Otherwise, what is the point to any of it?