| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: GO Fight Against Malaria
Thread: Stuck WUs |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
BSD
Senior Cruncher Joined: Apr 27, 2011 Post Count: 224 Status: Offline |
Task Manager shows no CPU activity for any BOINC WU related process, the project application and vina application for both WUs are still in memory just not showing CPU activity. Nothing in System or Application event viewer logs that would indicate a problem.
----------------------------------------Client OS: Windows 7 x64 RAM: 2 GB DDR2 CPU: AMD Athlon(tm) 64 X2 Dual-Core Processor TK-53 WU: GFAM_x1j3k_NDP_dry_0000782_1049_0 Progress: 41% CPU Time: 04:03:22 Elapsed Time: 17:03:37 App: 6.08 WU: GFAM_x1j3k_NDP_dry_0000791_0305_0 Progress: 41.250% CPU Time: 04:28:39 Elapsed Time: 15:14:56 App: 6.08 Will suspend WU tasks, reboot computer, and resume WU tasks to get them going again. More wasted time and electricty.  EDIT: WUs completed - no "stuck" related comment in the completed result log, like nothing ever happened, yeah right.  GFAM_ x1j3k_ NDP_ dry_ 0000791_ 0305_ 0-- 608 Pending Validation 11/29/11 13:13:31 12/1/11 22:12:04 9.45 GFAM_ x1j3k_ NDP_ dry_ 0000782_ 1049_ 0-- 608 Valid 11/29/11 09:02:53 12/1/11 22:12:04 9.38 [Edit 1 times, last edit by BSD at Dec 1, 2011 10:20:50 PM] |
||
|
|
Hypernova
Master Cruncher Audaces Fortuna Juvat ! Vaud - Switzerland Joined: Dec 16, 2008 Post Count: 1908 Status: Offline Project Badges: 
|
The following WU was stuck. It did display -100%, 9 hours remaining and the status was Running, but without any change in percentage.
----------------------------------------The thread was like stuck in a loop. I aborted it. Here under is the abort log: *********************************************** Result Name: GFAM_ x1j3iWt_ NDP_ dry_ 0000997_ 0097_ 1-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> aborted by user </message> <stderr_txt> INFO: No state to restore. Start from the beginning. [21:35:41] Number of tasks = 32 [21:35:41] Starting job 0,CPU time is 0.000000. [21:35:41] ./ZINC03380887.pdbqt size = 37 8 ../../projects/www.worldcommunitygrid.org/gfam.x1j3iWt_NDP_dry.pdbqt size = 2342 0 [21:53:57] Finished Job #0 cpu time used 1093.223808 [21:53:57] Starting job 1,CPU time is 1093.223808. [21:53:57] ./ZINC03380887.pdbqt size = 37 8 ../../projects/www.worldcommunitygrid.org/gfam.x1j3iWt_NDP_dry.pdbqt size = 2342 0 [22:01:38] Number of tasks = 32 [22:01:38] Starting job 1,CPU time is 1093.223808. [22:01:38] ./ZINC03380887.pdbqt size = 37 8 ../../projects/www.worldcommunitygrid.org/gfam.x1j3iWt_NDP_dry.pdbqt size = 2342 0 Abort requested: Exiting </stderr_txt> ]]> ********************************************************  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Task Manager shows no CPU activity for any BOINC WU related process, the project application and vina application for both WUs are still in memory just not showing CPU activity. Nothing in System or Application event viewer logs that would indicate a problem. Client OS: Windows 7 x64 RAM: 2 GB DDR2 CPU: AMD Athlon(tm) 64 X2 Dual-Core Processor TK-53 WU: GFAM_x1j3k_NDP_dry_0000782_1049_0 Progress: 41% CPU Time: 04:03:22 Elapsed Time: 17:03:37 App: 6.08 WU: GFAM_x1j3k_NDP_dry_0000791_0305_0 Progress: 41.250% CPU Time: 04:28:39 Elapsed Time: 15:14:56 App: 6.08 Will suspend WU tasks, reboot computer, and resume WU tasks to get them going again. More wasted time and electricty. EDIT: WUs completed - no "stuck" related comment in the completed result log, like nothing ever happened, yeah right. GFAM_ x1j3k_ NDP_ dry_ 0000791_ 0305_ 0-- 608 Pending Validation 11/29/11 13:13:31 12/1/11 22:12:04 9.45 GFAM_ x1j3k_ NDP_ dry_ 0000782_ 1049_ 0-- 608 Valid 11/29/11 09:02:53 12/1/11 22:12:04 9.38 Having a similar issue, stuck at 40%, restarted and now it says it is waiting for gpu memory.... is that normal? Haven't seen it before after restarting to "fix" a stuck unit.... |
||
|
|
|