Control: severity -1 minor

Your chroot is missing the sd_notify socket. The package can’t really expect 
all non-default configurations. I can probably add a NEWS.Debian entry for 
this, but it’s certainly not important severity.

Ondrej
--
Ondřej Surý <ond...@sury.org> (He/Him)

> On 14. 6. 2023, at 23:15, Bret Giddings <b...@essex.ac.uk> wrote:
> 
> Package: bind9
> Version: 1:9.18.12-1
> Severity: important
> 
> Dear Maintainer,
> 
> Whilst attempting to upgrade from debian 11 to 12, for my chroot named setup, 
> I
> found that running
> 
>    systemctl restart named
> 
> would hang and eventually timeout. It should be noted that named is running 
> fine.
> 
> Having compared the differences from 11 to 12, I believe that this is caused
> by the latter unit file using a service type of notify rather than the default
> simple.
> 
> Creating an override with
> 
>    [Service]
>    Type=simple
> 
> restores the former behaviour. So, I believe that the notify option is unable
> to communicate with the chroot'ed environment. Whilst I can use the above
> as a workaround, I couldn't find anything in the changelog or elsewhere
> reporting this issue. I also tested and confirmed this behaviour on a new
> install of bind9 with minimal customisation. It only fails when you switch
> to using '-t /var/cache/bind' in /etc/defaults/named (having previously
> created the appropriate directories etc.
> 
> 
> -- System Information:
> Debian Release: 12.0
>  APT prefers stable-security
>  APT policy: (500, 'stable-security'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Kernel: Linux 6.1.0-9-amd64 (SMP w/48 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages bind9 depends on:
> ii  adduser                    3.134
> ii  bind9-libs                 1:9.18.12-1
> ii  bind9-utils                1:9.18.12-1
> ii  debconf [debconf-2.0]      1.5.82
> ii  dns-root-data              2023010101
> ii  init-system-helpers        1.65.2
> ii  iproute2                   6.1.0-3
> ii  libc6                      2.36-9
> ii  libcap2                    1:2.66-4
> ii  libfstrm0                  0.6.1-1
> ii  libjson-c5                 0.16-2
> ii  liblmdb0                   0.9.24-1
> ii  libmaxminddb0              1.7.1-1
> ii  libnghttp2-14              1.52.0-1
> ii  libprotobuf-c1             1.4.1-1+b1
> ii  libssl3                    3.0.9-1
> ii  libsystemd0                252.6-1
> ii  libuv1                     1.44.2-1
> ii  libxml2                    2.9.14+dfsg-1.2
> ii  netbase                    6.4
> ii  sysvinit-utils [lsb-base]  3.06-4
> ii  zlib1g                     1:1.2.13.dfsg-1
> 
> bind9 recommends no packages.
> 
> Versions of packages bind9 suggests:
> pn  bind-doc                   <none>
> ii  bind9-dnsutils [dnsutils]  1:9.18.12-1
> pn  resolvconf                 <none>
> pn  ufw                        <none>
> 
> -- Configuration Files:
> /etc/bind/db.0 [Errno 2] No such file or directory: '/etc/bind/db.0'
> /etc/bind/db.127 [Errno 2] No such file or directory: '/etc/bind/db.127'
> /etc/bind/db.255 [Errno 2] No such file or directory: '/etc/bind/db.255'
> /etc/bind/db.empty [Errno 2] No such file or directory: '/etc/bind/db.empty'
> /etc/bind/db.local [Errno 2] No such file or directory: '/etc/bind/db.local'
> /etc/bind/named.conf changed [not included]
> /etc/bind/named.conf.default-zones [Errno 2] No such file or directory: 
> '/etc/bind/named.conf.default-zones'
> /etc/bind/named.conf.local [Errno 2] No such file or directory: 
> '/etc/bind/named.conf.local'
> /etc/bind/named.conf.options [Errno 2] No such file or directory: 
> '/etc/bind/named.conf.options'
> /etc/bind/zones.rfc1918 [Errno 2] No such file or directory: 
> '/etc/bind/zones.rfc1918'
> /etc/default/named changed [not included]
> 
> -- no debconf information
> 

Reply via email to