Message boards :
ATLAS application :
20 minutes remaining to 2 days
Message board moderation
Author | Message |
---|---|
Send message Joined: 5 May 22 Posts: 1 Credit: 254,438 RAC: 0 |
Curious as to why the 6 CPU application task says 20 minutes were remaining but the last few from 99.75% have taken days to accumulate? Is this particularly normal with LHC Atlas tasks? I've paused other tasks to possibly allow for extra resources to be given to the LHC application with no observable affect. |
Send message Joined: 27 Sep 08 Posts: 850 Credit: 692,828,532 RAC: 38,232 |
I think if you have don't done many tasks then there is error in how the remaining time calculated, it should get better over time. |
Send message Joined: 11 May 22 Posts: 3 Credit: 1,460,668 RAC: 0 |
I have the same problem 5 CPUs task done in 100%, working time so far 3 days 4:57:58 and still counting althout ending time shows 00:00:00 all other tasks are stopped ... |
Send message Joined: 15 Jun 08 Posts: 2541 Credit: 254,608,838 RAC: 15,673 |
You may make your computers visible for other volunteers first: https://lhcathome.cern.ch/lhcathome/prefs.php?subset=project |
Send message Joined: 11 May 22 Posts: 3 Credit: 1,460,668 RAC: 0 |
done |
Send message Joined: 15 Jun 08 Posts: 2541 Credit: 254,608,838 RAC: 15,673 |
I have the same problem 5 CPUs task done in 100%, working time so far 3 days 4:57:58 and still counting althout ending time shows 00:00:00 all other tasks are stopped ... This is most likely caused by too many suspend/resume cycles. See the logs from ATLAS/CMS. You got a mix of different tasks. Theory: works fine see: https://lhcathome.cern.ch/lhcathome/result.php?resultid=354205816 https://lhcathome.cern.ch/lhcathome/result.php?resultid=354202802 CMS: works fine https://lhcathome.cern.ch/lhcathome/result.php?resultid=354214457 except that CMS (and ATLAS) don't like to be suspended too often or for longer. This may become a problem in the future. 2022-05-12 16:57:06 (5864): VM state change detected. (old = 'running', new = 'paused') 2022-05-12 17:10:39 (5864): VM state change detected. (old = 'paused', new = 'running') 2022-05-12 17:12:52 (5864): VM state change detected. (old = 'running', new = 'paused') 2022-05-12 17:19:05 (5864): VM state change detected. (old = 'paused', new = 'running') . . . ATLAS WUs like this are caused by a CERN configuration error: https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=188417240 Just ignore them. These are fine as they returned a HITS file: https://lhcathome.cern.ch/lhcathome/result.php?resultid=354294703 https://lhcathome.cern.ch/lhcathome/result.php?resultid=354295020 https://lhcathome.cern.ch/lhcathome/result.php?resultid=354211799 2022-05-12 16:40:00 (11588): Guest Log: HITS file was successfully produced The last one suffered from suspend/resume described above but finally succeeded. Nonetheless it was close before a crash. 2022-05-11 23:03:46 (9856): Error in stop VM for VM: -108 |
Send message Joined: 11 May 22 Posts: 3 Credit: 1,460,668 RAC: 0 |
Thank you for deep explanations. |
©2025 CERN