| 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: 6
|
|
| Author |
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 638 Status: Offline Project Badges:
|
The power cut or blipped last night so 2 machines running WCG on Xubuntu were affected.
Upon reboot the BOINC Manager icon shows on the desktop but the GUI does not come up. The client is running. I see the CPU at 100 and taskmgr shows it is up. So I dug around and found boinccmd which let me suspend the project and reboot. This solved it. I know just rebooting would do it like last time. I presume I lost the task processing time done between the last checkpoint and power failure so not much time lost if I do the second reboot to fix the problem. Not too scientific and I would not have learnt about boinccmd. Now would killing the Manager via taskmgr have done the same or would this kill the running tasks? Instincts tell me no because if the GUI BOINCmgr is vital then why boinccmd. I will try this next time. Any insight? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Killing the manager does not kill the client daemon or the reverse. Each are separate processes that communicate via the RPC protocol.
When exiting BOINC Manager the normal way, default is that is asks if to end the client too. I've set it to not do so and remember i.e. it's not asking me again. The manager is the piece that uses CPU time when open, so I hardly ever run it. |
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 638 Status: Offline Project Badges:
|
Good to know. Killed all instances on all machines.
|
||
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 1316 Status: Offline Project Badges:
|
@BobbyB
----------------------------------------For information - if BOINC Manager won't start, look in your home directory for a file called something like BOINC Managerbobbyb (or whatever your userid might be if not bobbyb!) and delete it.; Note the space in the file name... It's a lock file which BOINC Manager creates on starting, and it contains the PID of that manifestation of the program. If that exists, it won't start another one via the icon or the XFCE menus, and it's unlikely to be deleted on a crash! Been there, done that... Cheers - Al. [Edited to fix a typo.] [Edit 1 times, last edit by alanb1951 at Jul 20, 2020 4:28:23 AM] |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges:
|
What also happens:
In your BOINC Manager you open the Event Log (and you keep the Event Log open). Then you close the BOINC Manager window instead of the Event Log window. Result: both disappear. Then all of a sudden the BOINC Manager doesn't want to start again. Reason: the Event Log process, as part of the BOINC Manager process, is still running and the lockfile still exists. Solution: one way is to remove the lockfile ($HOME/BOINC Manager-*), but that doesn't remove the Event Log process that is still running. You'd have to kill the Event Log process (*1) and then everything should be fine again. YMMV. (This is boinc-manager-7.16.6-3.fc31.x86_64 speaking.) (*1) PS Killing the process goes something like this: killall boincmgr |
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 638 Status: Offline Project Badges:
|
@alanb1951
Ah this is what I was looking for. I knew there had to be something like that. In any case I do not leave the manager open any more. Problem solved... and am looking at another UPS. |
||
|
|
|