My host is running Linux Mint 18.3 and it was working fine with Boinc 7.9.3.

After upgrading it to latest development release (from https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc ) Boinc Manager can't connect to localhost.

I don't know what's wrong. I didn't change anything else. I've tried to stop and restart Boinc Client before I start Boinc Manager, but that doesn't help.

There is a known problem with the source code for v7.10.1 - one of the bug-fixes relies on a precursor patch, and I missed that when calling the release 'ready'. I did issue a recall, but evidently not quickly enough. We'll get a v7.10.2 out as soon as I can find someone to transfer the missing patch: unfortunately, it's a complicated one I don't feel confident enough to tackle myself.

Edit - BOINC consists of two parts, the Client and the Manager. You'll have updated both, not just the Manager. It would be helpful to know whether your problem is

a) Both client and manager are running, but they can't communicate
b) The client ISN'T running, so there's nothing for the manager to connect to

Are you able to use operating system tools to check the status of the client, independently of the Manager connection? If the client fails to start, there might be error messages in the log files which could help us.

I am getting the same problem after installing 7.10.1 on Ubuntu 17.10.

The Manager starts but cannot connect to the client. The Client is NOT running.

I see these error messages at system boot in the syslog:

Apr 27 07:20:27 IRIS52 cron[707]: (CRON) INFO (pidfile fd = 3)
Apr 27 07:20:27 IRIS52 systemd[708]: boinc-client.service: Failed at step CHDIR spawning /usr/bin/boinc: No such file or directory
Apr 27 07:20:27 IRIS52 systemd[1]: Starting LSB: Load kernel modules needed to enable cpufreq scaling...
Apr 27 07:20:27 IRIS52 systemd[1]: Started CUPS Scheduler.
Apr 27 07:20:27 IRIS52 cron[707]: (CRON) INFO (Running @reboot jobs)
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Modem Manager...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting LSB: Start SDDM...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting System Logging Service...
Apr 27 07:20:27 IRIS52 dbus[685]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Thermal Daemon Service...
Apr 27 07:20:27 IRIS52 systemd[1]: Started Set the CPU Frequency Scaling governor.
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Network Manager...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Apr 27 07:20:27 IRIS52 systemd[1]: Reached target Login Prompts.
Apr 27 07:20:27 IRIS52 systemd[1]: Starting LSB: automatic crash report generation...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Save/Restore Sound Card State...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting LSB: Speech Dispatcher...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Disk Manager...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Login Service...
Apr 27 07:20:27 IRIS52 systemd[1]: Starting Snappy daemon...
Apr 27 07:20:27 IRIS52 systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 27 07:20:27 IRIS52 systemd[1]: Started System Logging Service.
Apr 27 07:20:27 IRIS52 systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
Apr 27 07:20:27 IRIS52 systemd[1]: boinc-client.service: Main process exited, code=exited, status=200/CHDIR
Apr 27 07:20:27 IRIS52 udisksd[735]: udisks daemon version 2.6.5 starting
Apr 27 07:20:27 IRIS52 ModemManager[713]:

This is what /usr/bin/boinc looks like:

john@IRIS52:/usr/bin$ ls boinc
boinc
john@IRIS52:/usr/bin$ ls boinc -al
-rwxr-xr-x 1 root root 973016 Apr 26 12:17 boinc
john@IRIS52:/usr/bin$ cd boinc
bash: cd: boinc: Not a directory
john@IRIS52:/usr/bin$ more boinc

******** boinc: Not a text file ********

john@IRIS52:/usr/bin$

Sorry... I didn't check on that carefully enough (I was super-tired, going to bed back then). Client actually wasn't running at all. It fails to start at boot-up and also fails to start anytime later.

I looked at the syslog and I see exactly the same error messages as JGREAVES.

Here is the procedure:
Client failed to start while boot-up.
Then, I run command: "sudo systemctl --no-pager stop boinc-client.service" ... just to make sure.
Then... I run command: "sudo systemctl --no-pager start boinc-client.service"
... and that does produce this:

... Started Berkeley Open Infrastructure Networking Computer Client ...
... boinc-client.service: Failed at step CHDIR spawning /usr/bin/boinc: No such file or directory
... boinc-client.service: Main process exited, code=exited, status=200/CHDIR
... boinc-client.service: Failed at step CHDIR spawning /usr/bin/boinccmd: No such file or directory
... boinc-client.service: Control process exited, code=exited status=200
... boinc-client.service: Failed at step CHDIR spawning /bin/rm: No such file or directory
... boinc-client.service: Control process exited, code=exited status=200
... boinc-client.service: Unit entered failed state
... boinc-client.service: Failed with result 'exit-code'.

This is a problem in Debian package. Maintainer missed a change to the file that is used to start the service. Debian #897130

Debian/Ubuntu/Mint/etc, all same.

Quoting the linked bug report:

WorkingDirectory option in boinc-client.service was changed from

WorkingDirectory=~

to

WorkingDirectory=/var/lib/boinc

in upstream PR 2419 and this prevents starting boinc-client on Debian based
distros. The change was because enterprisey distros have older systemd's that
don't support ~ in paths.

Just a thought from someone using BOINC 7.6.33 on Debian 9.4 with systemd 232. In that version BOINC does not include a service file and the Debian package has an own that does NOT set WorkingDirectory. man systemd.exec states:

If not set, defaults to the root directory when systemd is running as a system instance and the respective user's home directory if run as user.

I think that's just what's needed here if those older systemds use the same defaults.

7.6.33 on Debian 9.4 with systemd 232. In that version BOINC does not include a service file and the Debian package has an own that does NOT set WorkingDirectory.

That version starts the client with

/usr/bin/boinc --dir /var/lib/boinc-client

If not set, defaults to the root directory when systemd is running as a system instance and the respective user's home directory if run as user.

I think that's just what's needed here if those older systemds use the same defaults.

I believe that in this case, systemd starting boinc-client, systemd runs as system instance. So default wouldn't work.

There is a new BOINC version available now (still 7.10.1 ... but it's a new one). It fixed this problem. Client is able to run and Manager is able to connect to it.

There is a new BOINC version available now (still 7.10.1 ... but it's a new one). It fixed this problem. Client is able to run and Manager is able to connect to it.

Can you give me particulars of when and where this new package was released - which distros have access to it? I'll update the sticky warning message I put in Questions and problems yesterday.

Can you give me particulars of when and where this new package was released - which distros have access to it? I'll update the sticky warning message I put in Questions and problems yesterday.

It was available via ppa:costamagnagianfranco/boinc .
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc

Timestamp on the version name is 201805012009 ... so at the moment it was released about 15 hours ago.

Packages:
7.10.1+dfsg-0~201805012009~ubuntu18.04.1
7.10.1+dfsg-0~201805012009~ubuntu17.10.1
7.10.1+dfsg-0~201805012009~ubuntu16.04.1

My computers are running Linux Mint 18.3 and they use the 16.04.1 variant. At least that one is working. I don't know about the 17.10.1 or 18.04.1.

These packages are for Debian distros. Adding that untrusted PPA is required of course ... and "sudo apt-get update".[/url]

The version in Debian is 7.10.1+dfsg-2. Might take a few days before Debian release system makes it available.

Here's a handy page for package information.

I've sent out the release / rebuild instruction for v7.10.2 - hopefully that will resolve all the confusion.