[SOLVED] Unbound refuses to start

Question

Hi,
I've set up DNSCrypt and Unbound, as explained in the wiki. I've enabled systemd services both for DNSCrypt and Unbound and created configuration file, to have DNSCrypt started before Unbound.
Here is my /etc/systemd/system/dnscrypt-proxy.service.d/unbound.conf:
[Unit]
Before=unbound.service
DNSCrypt starts up just fine, however Unbound doesn't and I get following output, to systemctl status unbound -l command:
● unbound.service - Unbound DNS Resolver
Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled)
Active: failed (Result: start-limit) since Sun 2014-08-24 08:12:08 CEST; 52min ago
Process: 4949 ExecStart=/usr/bin/unbound -d (code=exited, status=1/FAILURE)
Main PID: 4949 (code=exited, status=1/FAILURE)
Aug 24 08:12:07 esme unbound[4949]: [1408860727] unbound[4949:0] fatal error: could not open ports
Aug 24 08:12:07 esme systemd[1]: unbound.service: main process exited, code=exited, status=1/FAILURE
Aug 24 08:12:07 esme systemd[1]: Unit unbound.service entered failed state.
Aug 24 08:12:08 esme systemd[1]: unbound.service start request repeated too quickly, refusing to start.
Aug 24 08:12:08 esme systemd[1]: Failed to start Unbound DNS Resolver.
Aug 24 08:12:08 esme systemd[1]: Unit unbound.service entered failed state.
The weird thing is, that sometimes Unbound will start, but I don't know on what it may depend. Does anyone have an idea, how to fix it?
Last edited by PiotrPyclik (2014-09-02 21:06:08)

Answer 1

The strange thing is, that half of the times dnscrypt-proxy and unbound start without any problem - in such case, I can also stop and start them manually. Last time, unbound failed to start and here is output I've got:
~ sc-status unbound
● unbound.service - Unbound DNS Resolver
Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled)
Active: failed (Result: start-limit) since Tue 2014-08-26 21:31:10 CEST; 4s ago
Process: 1834 ExecStart=/usr/bin/unbound -d (code=exited, status=1/FAILURE)
Main PID: 1834 (code=exited, status=1/FAILURE)
Output stays exactly the same, regardless of status of dnscrypt-proxy.  Also, it is different than in my first post. I don't know why, because I haven't changed configuration.
Here is my netstat -lutnp:
~ _ netstat -lutnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 236/connmand
tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN 254/privoxy
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 265/btsync
tcp 0 0 0.0.0.0:62204 0.0.0.0:* LISTEN 265/btsync
tcp6 0 0 ::1:53 :::* LISTEN 236/connmand
udp 0 0 127.0.0.1:37504 0.0.0.0:* 265/btsync
udp 0 0 0.0.0.0:62204 0.0.0.0:* 265/btsync
udp 0 0 0.0.0.0:3838 0.0.0.0:* 265/btsync
udp 0 0 0.0.0.0:1900 0.0.0.0:* 265/btsync
udp 0 0 0.0.0.0:59303 0.0.0.0:* 233/systemd-timesyn
udp 0 0 127.0.0.1:53 0.0.0.0:* 236/connmand
udp 0 0 192.168.0.101:49312 0.0.0.0:* 265/btsync
udp6 0 0 ::1:53 :::* 236/connmand