| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Human Proteome Folding - Phase 2
Thread: No status... |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
mtughan
Cruncher Joined: Jan 10, 2007 Post Count: 2 Status: Offline |
On an HPF2 WU running on a 2.0GHz Core Duo Macbook with HPF 5.19, I'm not getting any status updates from BOINC. They've been running for about 5h now, and it still says 0.00%, and when I go to the graphics, the window opens, but everything's at default values. I have been experiencing problems with this over the past few days, where the WU wouldn't stop when I slept BOINC. I'm just wondering if I should let it go on, or abort the WU. I have two of them, and both are exhibiting the same behaviour. Also, the kernel starts using an abnormal amount of CPU space when it's running. It normally takes about 5-10% CPU power. When the WUs are running, it goes up to 40-50%.
----------------------------------------[Edit 1 times, last edit by mtughan at Aug 15, 2007 10:08:25 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello mtughan,
I think that you have run into a known bug in HPF2 that we have never been able to track down. Occasionally HPF2 will seem to get caught in an infinite loop. Ordinarily, the way to clear it is to Suspend the Project (World Community Grid ) in BOINC Manager for about 30 seconds, then unsuspend it. The work unit will start up again from the last check point and this time will run to completion. In your case it seems to have gone into a loop before writing a checkpoint, so the easiest thing is probably to Exit BOINC and then reboot. It is hard to locate the bug because it is not repeatable. The same computer, running the same work unit, will not encounter this bug a second time. sigh . . . Lawrence |
||
|
|
mtughan
Cruncher Joined: Jan 10, 2007 Post Count: 2 Status: Offline |
Okay, well thanks for the advice. I was away for a few days, and it was given a computation error while I was gone. I'll keep that in mind for the next time it happens. Thanks.
|
||
|
|
|