[Pkg-dns-devel] Bug#883575: Bug#883575: bind9: bind 9 doesn't start after update

[Bernhard Schmidt]

Control: tag -1 + confirmed

On 05.12.2017 12:30, Elimar Riesebieter wrote:

Hi Elimar,

thanks for your report.

> Package: bind9
> Version: 1:9.11.2+dfsg-4
> Severity: important
> 
> Upgrade on a sysvinit driven system gives:
> 
> Starting domain name service...: bind9.
> Starting domain name service...: bind9 failed!

This looks like bind9 is started twice.

>   Dec  5 12:23:06 baumbart named[3902]: using default UDP/IPv4 port range: [32768, 60999]¬
>   Dec  5 12:23:06 baumbart named[3902]: using default UDP/IPv6 port range: [32768, 60999]¬
>   Dec  5 12:23:06 baumbart named[3902]: listening on IPv6 interfaces, port 53¬
>   Dec  5 12:23:06 baumbart named[3902]: binding TCP socket: address in use¬

Thus the second process complains that it cannot bind to any port and fails.

Preliminary debugging indeed shows that it will be executed twice.

=== bind9.postinst ===
if [ "$1" = configure ]; then
[...]
    if pidof /usr/sbin/named >/dev/null 2>&1; then
        invoke-rc.d bind9 restart
    else
        invoke-rc.d bind9 start
    fi
fi

[...]

# Automatically added by dh_installinit/10.10.9
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ]; then
        if [ -x "/etc/init.d/bind9" ]; then
                update-rc.d bind9 defaults >/dev/null
                invoke-rc.d bind9 start || exit $?
        fi
fi
===

which is not a problem on systemd, but on sysvinit.

We should probably drop the hand-written part and have dh_installinit
handle it for us. If prerm didn't properly stop it we probably have
larger issues.

Bernhard