Apologies if this is posted elsewhere; my own search didn't turn it up. Please redirect me if you know of a previously submitted solution.

I installed boinc (7.2.42 x86_64-suse-linux-gnu) on opensuse leap 42.1. When I open boinc manager in X, it can't connect to localhost. When I run boinc in a terminal, it chirps along merrily all night long.

Then, if I've started boinc by CLI, I can open boinc manager & connect to 127.0.0.1 with the pass in gui_rpc_auth.cfg. However, if I open boinc manager while boinc is not running, it will not connect. Sometimes it will tell me that the boinc client has unexpectedly quit 3 or 4 times in the past 3 to 5 minutes (the numbers change each time I see this dialog).

Yet, running boinc from CLI, then either starting the gui manager or not, seems to achieve normal, stable operation. Having run boinc on win7 and debian, I never needed to use a CLI pre-launch. What is wrong with my setup in opensuse?

However, if I open boinc manager while boinc is not running, it will not connect.

That's normal. Under Linux starting BOINC Manager does not auto-start the client. You always have to start the client first, then the manager.

That it connects to a running client is normally because packaged-by-the-OS-BOINC is set up to run as a daemon, so at some point during OS start, and when you then start the manager, it'll connect (if locally allowed through firewalls).

Open a terminal and enter ps aux | grep boinc to print a partial list of running processes. You should see boinc_client --daemon in that list. If you do not, the install went wrong and you'll have to reinstall.

---

Thank you for the swift reply. Since this is my first time running opensuse's version boinc package, I learned a bit from your post. I seem to recall (maybe confabulating) different behaviour running the debian packaged version, or the win7 version of boinc.

Running the terminal command you recommended doesn't return boinc_client --daemon, nor is it listed in the process list of System Monitor, though boinc is successfully running tasks on all available threads. I will try uninstalling boinc completely, then re-installing it.

It may seem like I'm trying to fix something that isn't really broken, but I don't think I should have to keep the terminal window open where I started boinc, while it is running, especially if I want to keep the boinc manager gui open alongside. So, I guess I need to repair the daemon installation/implementation/execution...

OK, now back to the tinkering shed!

In case your distro's BOINC does not do BOINC as a daemon out of the box, you can see how to set that up at http://boinc.berkeley.edu/wiki/Stop_or_start_BOINC_daemon_after_boot

---