Message boards : Number crunching : Tasks run for over 30 hours
Author | Message |
---|---|
shauge Send message Joined: 10 Dec 05 Posts: 5 Credit: 17,769,405 RAC: 31,111 |
I do now have several tasks on different machines that have run for over 30 hours and are estimated to be less than 50% through. Should I abort those tasks or let them run? I have not changed the default running length target. |
Sid Celery Send message Joined: 11 Feb 08 Posts: 2117 Credit: 41,157,923 RAC: 15,823 |
I do now have several tasks on different machines that have run for over 30 hours and are estimated to be less than 50% through. Should I abort those tasks or let them run? The watchdog should cut in after runtime+4 hours, so it sounds like the WU has stopped processing. Select the WU in Boinc Manager, then click properties to see the difference between elapsed time & cpu time. Task manager will show if it's actually using any resources. Try shutting down Boinc then restart it and see if it actually starts processing properly. Hopefully that won't lose the processing you've actually completed. If not, it sounds like the task has to be aborted, unfortunately. |
shauge Send message Joined: 10 Dec 05 Posts: 5 Credit: 17,769,405 RAC: 31,111 |
so it sounds like the WU has stopped processing. It looks like you were right, the WUs had actually stopped processing. Thanks for your help :) This means that I now have to babysit my machines :( |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
Has anyone seen any word from the BOINC folks on reasolution to this problem where the BOINC Manager thinks the task is running, but it gets no CPU time? The good news is that it seems to be fairly rare. The bad news is you typically have to exit and restart BOINC for it to work through the problem. Rosetta Moderator: Mod.Sense |
Message boards :
Number crunching :
Tasks run for over 30 hours
©2024 University of Washington
https://www.bakerlab.org