[solved] dnscrypt-proxy sometimes fails to start during boot (ordering cycle)

[littlehuman]

Hello,

Running Linux Mint 18.3 Cinnamon 64-bit on a laptop with wifi, I installed dnscrypt-proxy 1.6.1-1 from the Software manager.
It runs fine, except that sometimes it doesn't start and I have to manually start it.

Investigating this, I checked the syslog and found this :

Code: Select all

[5.889235] systemd[1]: sockets.target: Found ordering cycle on sockets.target/start
[5.889238] systemd[1]: sockets.target: Found dependency on dnscrypt-proxy.socket/start
[5.889240] systemd[1]: sockets.target: Found dependency on network.target/start
[5.889241] systemd[1]: sockets.target: Found dependency on NetworkManager.service/start
[5.889243] systemd[1]: sockets.target: Found dependency on basic.target/start
[5.889244] systemd[1]: sockets.target: Found dependency on sockets.target/start
[5.889246] systemd[1]: sockets.target: Breaking ordering cycle by deleting job dnscrypt-proxy.socket/start

Searching the Internet, I found this interesting page : https://groups.google.com/forum/#!msg/l ... 1VRwQeAwAJ
On this page (see below quote), they even say how to fix it, but as I'm quite a newbie in Linux (Windows refugee), I don't understand what it implies/means.

Bug#832933: dnscrypt-proxy: dnscrypt-proxy.socket should not be After network.target
This was corrected upstream in 1.6.1 [1][2], but the Debian/Ubuntu
package has its own systemd units in the debian/ directory, possibly
derived from the ones shipped in 1.6.0. Please apply the Debian
customizations via drop-ins (see systemd.unit(5)) or by patching the
units like you'd do for any other change to the upstream source code, or
re-sync the ones in debian/ with those supplied by upstream.

Ok, but how can I do this and/or what would you suggest to fix this properly ?

Other technical info

Code: Select all

System:    Host: spinoza Kernel: 4.4.0-109-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.3 Sylvia
Network:   Card-1: Intel Centrino Advanced-N 6235 driver: iwlwifi bus-ID: 03:00.0
           IF: wlp3s0 state: up mac: <filter>
           Card-2: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet
           driver: atl1c v: 1.0.1.1-NAPI port: d000 bus-ID: 04:00.0
           IF: enp4s0 state: down mac: <filter>          

[littlehuman]

Posting this problem I didn't even know dnscrypt-proxy.socket was a file. Long life to newbies !
I learned a lot about services and systemd.

FWIW, issue seems to be fixed by having removed following line

Code: Select all

After=network.target

from /lib/systemd/system/dnscrypt-proxy.socket

Before this change, command systemd-analyze verify default.target returned

Code: Select all

	basic.target: Found ordering cycle on basic.target/start
	basic.target: Found dependency on sockets.target/start
	basic.target: Found dependency on dnscrypt-proxy.socket/start
	basic.target: Found dependency on network.target/start
	basic.target: Found dependency on NetworkManager.service/start
	basic.target: Found dependency on dbus.service/start
	basic.target: Found dependency on basic.target/start
	basic.target: Breaking ordering cycle by deleting job sockets.target/start
	sockets.target: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start

After the change, no ordering cycle anymore.
After 10 reboots, dnscrypt is always up and running. Satisfying.

[majpooper]

THX littlehuman - was living with the same issue and was just starting up the dnscrypt-proxy after reboot as a matter of course - not a big deal but nice not to have to do it every time.

[littlehuman]

You're welcome. I'm glad it may help others.