Control: severity -1 important

Marcel,

I can’t reproduce it, so it must be some local configuration that’s causing 
your bind to exit.

can you attach output of:

systemctl status bind9

and contents of

/etc/default/bind9

And perhaps full output of

journalctl —unit=bind9 -b

since the last:

systemd[1]: Starting BIND Domain Name Server...

entry?

Ondrej
--
Ondřej Surý
ond...@sury.org



> On 6 Aug 2018, at 19:34, Marcel Veldhuizen <mar...@subbot.net> wrote:
> 
> Package: bind9
> Version: 1:9.11.4+dfsg-4
> Severity: grave
> Justification: renders package unusable
> 
> Dear maintainer,
> 
> Yesterday I upgraded 1:9.11.3+dfsg-2 to 1:9.11.4+dfsg-4, which appears
> to break something in the startup process of the service. Exactly 30 seconds
> after "service bind9 start" it is automatically shut down again.
> 
> For example, right after upgrading:
> 
> Aug 06 18:21:25 hellfire systemd[1]: Starting BIND Domain Name Server...
> Aug 06 18:21:25 hellfire systemd[1]: bind9.service: Control process exited, 
> code=exited status=1
> Aug 06 18:21:25 hellfire systemd[1]: bind9.service: Failed with result 
> 'exit-code'.
> Aug 06 18:21:25 hellfire systemd[1]: Failed to start BIND Domain Name Server.
> dpkg: error processing package bind9 (--configure):
> installed bind9 package post-installation script subprocess returned error 
> exit status 1
> 
> Nothing remarkable is logged; it appears to be a "normal" shutdown:
> 
> Aug  6 19:08:53 hellfire named[27030]: running
> Aug  6 19:08:54 hellfire named[27030]: managed-keys-zone: Key 19036 for zone 
> . acceptance timer complete: key now trusted
> Aug  6 19:08:54 hellfire named[27030]: managed-keys-zone: Key 20326 for zone 
> . acceptance timer complete: key now trusted
> Aug  6 19:08:54 hellfire named[27030]: resolver priming query complete
> Aug  6 19:10:23 hellfire named[27030]: shutting down
> Aug  6 19:10:23 hellfire named[27030]: stopping command channel on 
> 127.0.0.1#953
> Aug  6 19:10:23 hellfire named[27030]: stopping command channel on ::1#953
> Aug  6 19:10:23 hellfire named[27030]: no longer listening on ::#53
> Aug  6 19:10:23 hellfire named[27030]: no longer listening on 127.0.0.1#53
> Aug  6 19:10:23 hellfire named[27030]: no longer listening on 192.168.0.1#53
> Aug  6 19:10:23 hellfire named[27030]: exiting
> 
> I suspect it has something to do with this change:
> * Use systemd Type=forking to signal daemon init.
>  Thanks to Elie Roudninski (Closes: #900788)
> 
> I've tried reverting my config files to package defaults, but this makes
> no difference. Unfortunately I'm not sure what else I should check with
> regards to systemd configuration that might affect this, but I'd be
> happy to provide additional information.
> 
> 
> Regards,
> Marcel Veldhuizen
> 
> -- System Information:
> Debian Release: buster/sid
>  APT prefers testing
>  APT policy: (990, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.13.4 (SMP w/8 CPU cores)
> Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US 
> (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages bind9 depends on:
> ii  adduser                3.117
> ii  bind9utils             1:9.11.4+dfsg-4
> ii  debconf [debconf-2.0]  1.5.69
> ii  dns-root-data          2018013001
> ii  libbind9-160           1:9.11.4+dfsg-4
> ii  libc6                  2.27-5
> ii  libcap2                1:2.25-1.2
> ii  libcom-err2            1.44.3-1
> ii  libdns1102             1:9.11.4+dfsg-4
> ii  libfstrm0              0.3.0-1+b1
> ii  libgeoip1              1.6.12-1
> ii  libgssapi-krb5-2       1.16-2
> ii  libisc169              1:9.11.4+dfsg-4
> ii  libisccc160            1:9.11.4+dfsg-4
> ii  libisccfg160           1:9.11.4+dfsg-4
> ii  libjson-c3             0.12.1-1.3
> ii  libk5crypto3           1.16-2
> ii  libkrb5-3              1.16-2
> ii  liblmdb0               0.9.22-1
> ii  liblwres160            1:9.11.4+dfsg-4
> ii  libprotobuf-c1         1.2.1-2
> ii  libssl1.1              1.1.0h-4
> ii  libxml2                2.9.4+dfsg1-7+b1
> ii  lsb-base               9.20170808
> ii  net-tools              1.60+git20161116.90da8a0-3
> ii  netbase                5.4
> ii  zlib1g                 1:1.2.11.dfsg-1
> 
> bind9 recommends no packages.
> 
> Versions of packages bind9 suggests:
> pn  bind9-doc   <none>
> pn  dnsutils    <none>
> pn  resolvconf  <none>
> pn  ufw         <none>
> 
> -- Configuration Files:
> /etc/bind/db.root changed [not included]
> 
> -- debconf information:
>  bind9/different-configuration-file:
>  bind9/run-resolvconf: false
>  bind9/start-as-user: bind
> 

Reply via email to