| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Possible problem work unit |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
David_L6
Senior Cruncher USA Joined: Aug 24, 2006 Post Count: 296 Status: Offline Project Badges: 
|
I have a wu that's been running 21.5 hours, 2.464% progress, and 25+ hours to completion. That is not normal for the computer it is running on.
----------------------------------------The work unit is: Human Proteome Folding 2 lb132_ 00009_ 6-- I'm running BOINC 5.8.11.  |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Simply check on the details by clicking on the Work Unit Name in the Result Status page. If most all returned without error, consider to abort. At this pace it's going to miss thedeadline.
----------------------------------------If you confirm here with computer ID, OS etc, we'll advice the technicians. If it repeats on the next, consider to do a thorough antiviral/antibot/antispam check.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
olympic
Senior Cruncher Joined: Jun 12, 2005 Post Count: 156 Status: Offline |
I've had the same thing happen with HPF2, sometimes the WU just gets "stuck". Try this: go to the Projects tab and click on WCG and then click "suspend". Wait about a minute and then click "resume". With any luck the problem WU will resume and carry on to completion successfully. If suspend/resume doesn't work, try exiting BOINC altogether and then restart it. These 2 methods have worked 100% for me so far.
----------------------------------------Strangely though, the CPU time shown in BOINC will revert back to whatever it was when the WU became stuck. No trace of the 24hr+ it supposedly crunched away fruitlessly.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That's because when BOINC picks up from a checkpoint, it starts the CPU clock from the accumulated time at the checkpoint.
On the plus side, this means that people who manage their crunching more efficiently can get a higher score my minimising lost time. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
I've had the same thing happen with HPF2, sometimes the WU just gets "stuck". Try this: go to the Projects tab and click on WCG and then click "suspend". Wait about a minute and then click "resume". With any luck the problem WU will resume and carry on to completion successfully. If suspend/resume doesn't work, try exiting BOINC altogether and then restart it. These 2 methods have worked 100% for me so far. Strangely though, the CPU time shown in BOINC will revert back to whatever it was when the WU became stuck. No trace of the 24hr+ it supposedly crunched away fruitlessly. One can always consider upgrading to the latest recommended version. From 5.8.16 there is the '<checkpoint_debug>' feature, which I've got permanently switched on. It's covered in the Start Here, Checkpoint Saving post. It records all saves in the message tab of BOINC and indicates progress even if the percent is off or stuck.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|