| 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: 5
|
|
| Author |
|
|
lgcota
Cruncher Mexico Joined: Jul 28, 2011 Post Count: 5 Status: Offline Project Badges:
|
It's been many days since I see the paused BOINC icon on the taskbar of my Linux. As far as I can recall, I haven't deliberately paused it, and, as I see from the stats, it is not only when I'm using it, as the productivity of my machine slumped. In the interim I haven't messed with the settings.
I tried aborting the pending jobs and even reinstalling BOINC, to no avail. The system log now shows that it has recently downloaded more jobs, but they are not yet being executed. BOINC still appears pause. I'd appreciate your feedback. Thanks. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Open BOINC Manager and
1) In the project tab, what's the status for WCG? 2) In the Activity menu, what Run CPU line is selected? 3) Do Ctrl+Shft+E, browse through event log and read if any hints at pausing because of User activity oor other reason. Post copy of log so we can read if you don't see anything that rings a bell. |
||
|
|
lgcota
Cruncher Mexico Joined: Jul 28, 2011 Post Count: 5 Status: Offline Project Badges:
|
It says "100%", SekeRob.
In the Activity tab, preference-based options are selected. Nothing happens with Ctrl+Shft+E, but Shift+E brings about the activity log, whose last entries are an alternation of "suspending computation" and "resuming computation". I found out I had some runaway process on my system, and as soon as I killed it, WCG resumed execution. (Duh!) Thank you very much for your help. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Runaway process... if it happens to be appstreamcli then I posted a solution for that.
|
||
|
|
lgcota
Cruncher Mexico Joined: Jul 28, 2011 Post Count: 5 Status: Offline Project Badges:
|
It was actually some silly process that had to do with the window manager, SekeRob.
But thanks anyway. |
||
|
|
|