Bug#818370: [Pkg-dns-devel] Bug#818370: Fails to bind ports but suggests it started

also sprach Robert Edmonds [2016-07-05 00:50 +0200]: > 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) Thanks for following up! -- .''`.

Bug#818370: [Pkg-dns-devel] Bug#818370: Fails to bind ports but suggests it started

martin f krafft wrote: > also sprach martin f krafft [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

Bug#818370: Fails to bind ports but suggests it started

also sprach martin f krafft [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. -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `.

Bug#818370: Fails to bind ports but suggests it started

Package: unbound Version: 1.5.8-1 Severity: normal Starting unbound.service yields the following, which means that unbound was started, startup failed, but systemd thinks everything is fine. ● unbound.service Loaded: loaded (/etc/init.d/unbound; bad; vendor preset: enabled) Drop-In: