| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
ncaraway
Cruncher Joined: Feb 4, 2019 Post Count: 5 Status: Offline Project Badges:
|
I've had two ARP tasks over the past two weeks that seem to get stuck and their status remains at "Waiting to run". The first was at 95%. I tried to not allow new tasks to see if it would complete if it was the only task. The status never changed, so I aborted it. Now it has happened with another task, this time at 14%. I've returned 22 results for this project, so my PC is up to the job. I'm not sure what's going on, though. Any thoughts or suggestions?
|
||
|
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges:
|
The ones that I had in that state I left alone and they run to finish.
---------------------------------------- |
||
|
|
Clive Duffy
Cruncher Joined: Jan 14, 2010 Post Count: 4 Status: Offline Project Badges:
|
I have the same problem, this had happened after my laptop came out of hibernation. I am running Windows 10 and have this problem with both BOINC 7.14.2 and 7.16.5
I used to have BOINC running as a service install and found that by stopping the BOINC service, waiting a few seconds and then starting it again that it would start running again. Clocking "restart" on the service didn't fix this issue. I now have BOINC running under my account (a problem I think relating to work organisation constraints on managing user accounts) and have not been able to get this ARP project running atfer having restarted BOINC manager |
||
|
|
ncaraway
Cruncher Joined: Feb 4, 2019 Post Count: 5 Status: Offline Project Badges:
|
I installed the new BOINC update for Windows. That seems to have resolved the problem. Whew! Many thanks for the replies.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
7.16.5 had, per a volunteer contributor, a very large 'and complicated' scheduling code revision to deal with 'resource starvation' when max_concurrent is used in app_config. Maybe that fixed yours or a related problem.
|
||
|
|
Clive Duffy
Cruncher Joined: Jan 14, 2010 Post Count: 4 Status: Offline Project Badges:
|
I still have the problem with 7.16.5.
It seems to happen after the laptop comes out of hibernation, but doesn't seem to happen every time it comes out of hibernation!? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Before closing the lid, suspend BOINC. When coming out of hibernation wait a minute then resume BOINC. Who knows, those in-situ models in memory are big and need restoring in full before crunching can recommence.
|
||
|
|
Clive Duffy
Cruncher Joined: Jan 14, 2010 Post Count: 4 Status: Offline Project Badges:
|
After coming out of hibernation I noticed ARP was "Waiting to start"
I tried "Snooze" BOINC (from the tray icon), paused and resumed, but still wouldn't start. I shutdown the client and BOINC manager, then restarted BOINC Manager and it ran OK. I cannot use service install as my companies policy seems to restrict the setup of the service account I left an ARP running for the day, then decided to try Snooze from the tray icon. Then left it for 30 seconds before releasing it. This again shows as "Waiting to start". I've selected "No new tasks" and once the other tasks had complete (ARP was the only task remaining) it still would not start running. As an alternate test, once I had restarted BOINC manager and ARP was then running, I then unplugged the power cable (my laptop is setup to only run BOINC when plugged in), waited and plugged in the power again. But this time it started up without problem! Any ideas or suggestions please? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Have you looked in the client log to see if more details are available to explain the reason for the wait? Such as for memory or disk space.
|
||
|
|
Clive Duffy
Cruncher Joined: Jan 14, 2010 Post Count: 4 Status: Offline Project Badges:
|
An update, in case it is of use for others
I ticked some of the extra logs for scheduling, CPU etc, but couldn't glean anything obvious from it. I noticed that the processes were all stopping when snoozed or on battery and found the "Leave non-CPU tasks in memory while suspended" was unticked, since leaving in memory I have not had the problem, so at least a non-intrusive work around |
||
|
|
|