Boinc starting at boot and am I attached or not? Errors with Boinc Manager

Message boards : Questions and problems : Boinc starting at boot and am I attached or not? Errors with Boinc Manager
Message board moderation

To post messages, you must log in.

AuthorMessage
jeffmr4

Send message
Joined: 10 Feb 19
Posts: 2
United States
Message 89988 - Posted: 10 Feb 2019, 13:10:17 UTC

Boinc version 7.93 x64, Linux Mint 19.1, World Community Grid

I have two problems.

One is that the client starts automatically when I boot. I see many instances of wcgrid_mcm1_map running in top. I wanted to try to stop it from booting at startup so I did update-rc.d boinc-client remove in the terminal and rebooted. That didn't stop the service from starting so I opened the Boinc Manager GUI, switched it to Advanced View and went to Options -> Other options and unchecked 'run' under one of the tabs. It didn't say much but I guessed it might be run at startup. After I did that, the wcgrid_mcm1_map instances start at boot but when I connect to the Boinc Manager GUI all menus from View to the right have all their options greyed out.

When I do boinccmd --get_state I get Authorization failure -155. If I do this as root I see that my Account is not attached. So I do boinccmd --project_attach www.worldcommunitygrid.org <my account key> and get GUI RPC error: Already attached to project.

I tried using the key in gui_rpc_auth.cfg to attach to the project and the one on My Profile page but neither seems to work. I also found a lockfile in my home directory which I deleted after reading of someone else having a similar problem, deleting theirs and then everything working. I have had problems after deleting lockfiles before but I had run out of options so tried that.

Any help is greatly appreciated.
ID: 89988 · Report as offensive
jeffmr4

Send message
Joined: 10 Feb 19
Posts: 2
United States
Message 89989 - Posted: 10 Feb 2019, 15:18:50 UTC - in response to Message 89988.  

I found that if I deleted the password in gui_rpc_auth.cfg, started the Boinc Manager GUI, selected File -> Select computer and entered a host of 127.0.0.1 with no password it now starts. I also re-enabled the run at Boinc Manager startup in the Other -> Other options menu.
ID: 89989 · Report as offensive
jglrogujgv

Send message
Joined: 6 Jul 18
Posts: 49
Barbados
Message 90135 - Posted: 15 Feb 2019, 3:53:38 UTC - in response to Message 89988.  

Boinc version 7.93 x64, Linux Mint 19.1, World Community Grid

I have two problems.

One is that the client starts automatically when I boot. I see many instances of wcgrid_mcm1_map running in top. I wanted to try to stop it from booting at startup so I did update-rc.d boinc-client remove in the terminal and rebooted. That didn't stop the service from starting so I opened the Boinc Manager GUI, switched it to Advanced View and went to Options -> Other options and unchecked 'run' under one of the tabs. It didn't say much but I guessed it might be run at startup. After I did that, the wcgrid_mcm1_map instances start at boot...


The update-rc.d command requires root privileges. Did you run it as root? If that does not disable the daemon on boot then try the service command or the more recent systemctl command (recommended).

If you do "man systemctl" you'll see it has numerous options/arguments. The ones you are most likely interested in are: start, stop, enable, disable and status. They are used as follows:
sudo systemctl status boinc-client       (outputs like running, dead, stopped along with pertinent bits of the client's log)
sudo systemctl start boinc-client       (starts a stopped daemon, does NOT cause a disabled daemon to autostart at boot time)
sudo systemctl stop boinc-client        (stops a running daemon, does NOT prevent an enabled daemon from starting at boot time)
sudo systemctl enable boinc-client      (causes daemon to autostart at boot time, does NOT stop a running daemon)
sudo systemctl disable boinc-client      (prevents daemon autostart at boot time, does NOT halt a running daemon) 

Another problem you're running into is that you're relying on feedback from top and boinc to tell you whether the boinc daemon is running or not. As you've noted, that approach can be problematic. Instead use "sudo systemctl status boinc-client".
ID: 90135 · Report as offensive

Message boards : Questions and problems : Boinc starting at boot and am I attached or not? Errors with Boinc Manager

Copyright © 2019 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.