martin f krafft wrote:
> also sprach martin f krafft <[email protected]> [2016-03-16 15:05 +0100]:
> > I have no idea why it failed to bind the port on ::1. Nothing else
> > has this port bound.
>
> The loopback interface was not up.
I can replicate this bug with unbound 1.5.8-1, but not with 1.5.9-1. It
looks like it was fixed by:
* debian/unbound.init: Add "pidfile" magic comment (Closes: #807132)
This is with 1.5.9-1:
root@debian:~# systemctl stop unbound.service
root@debian:~# systemctl status unbound.service
● unbound.service
Loaded: loaded (/etc/init.d/unbound; generated; vendor preset: enabled)
Drop-In: /run/systemd/generator/unbound.service.d
└─50-insserv.conf-$named.conf, 50-unbound-$named.conf
Active: inactive (dead) since Mon 2016-07-04 22:47:42 UTC; 1s ago
Docs: man:systemd-sysv-generator(8)
Process: 2650 ExecStop=/etc/init.d/unbound stop (code=exited,
status=0/SUCCESS)
Process: 2535 ExecStart=/etc/init.d/unbound start (code=exited,
status=0/SUCCESS)
Main PID: 2547 (code=exited, status=0/SUCCESS)
Jul 04 22:47:03 debian unbound[2547]: [2547:0] notice: init module 1: iterator
Jul 04 22:47:03 debian unbound[2547]: [2547:0] info: start of service (unbound
1.5.9).
Jul 04 22:47:03 debian unbound[2535]: Starting DNS server: unbound.
Jul 04 22:47:03 debian systemd[1]: Started unbound.service.
Jul 04 22:47:42 debian systemd[1]: Stopping unbound.service...
Jul 04 22:47:42 debian unbound[2547]: [2547:0] info: service stopped (unbound
1.5.9).
Jul 04 22:47:42 debian unbound[2547]: [2547:0] info: server stats for thread 0:
0 queries, 0 answers from cache, 0 recursions,...refetch
Jul 04 22:47:42 debian unbound[2547]: [2547:0] info: server stats for thread 0:
requestlist max 0 avg 0 exceeded 0 jostled 0
Jul 04 22:47:42 debian unbound[2650]: Stopping DNS server: unbound.
Jul 04 22:47:42 debian systemd[1]: Stopped unbound.service.
Hint: Some lines were ellipsized, use -l to show in full.
root@debian:~# ifdown lo
root@debian:~# systemctl start unbound.service
Job for unbound.service failed because of unavailable resources or another
system error.
See "systemctl status unbound.service" and "journalctl -xe" for details.
root@debian:~# systemctl status -l unbound.service
● unbound.service
Loaded: loaded (/etc/init.d/unbound; generated; vendor preset: enabled)
Drop-In: /run/systemd/generator/unbound.service.d
└─50-insserv.conf-$named.conf, 50-unbound-$named.conf
Active: failed (Result: resources) since Mon 2016-07-04 22:47:56 UTC; 24s ago
Docs: man:systemd-sysv-generator(8)
Process: 2650 ExecStop=/etc/init.d/unbound stop (code=exited,
status=0/SUCCESS)
Process: 2692 ExecStart=/etc/init.d/unbound start (code=exited,
status=0/SUCCESS)
Main PID: 2547 (code=exited, status=0/SUCCESS)
Jul 04 22:47:55 debian systemd[1]: Starting unbound.service...
Jul 04 22:47:56 debian unbound-anchor[2699]: /var/lib/unbound/root.key has
content
Jul 04 22:47:56 debian unbound-anchor[2699]: success: the anchor is ok
Jul 04 22:47:56 debian unbound[2692]: Starting DNS server: unbound[1467672476]
unbound[2703:0] error: can't bind socket: Cannot assign requested address for
::1
Jul 04 22:47:56 debian unbound[2692]: [1467672476] unbound[2703:0] fatal error:
could not open ports
Jul 04 22:47:56 debian unbound[2692]: failed!
Jul 04 22:47:56 debian systemd[1]: unbound.service: PID file /run/unbound.pid
not readable (yet?) after start: No such file or directory
Jul 04 22:47:56 debian systemd[1]: Failed to start unbound.service.
Jul 04 22:47:56 debian systemd[1]: unbound.service: Unit entered failed state.
Jul 04 22:47:56 debian systemd[1]: unbound.service: Failed with result
'resources'.
root@debian:~#
--
Robert Edmonds
[email protected]
