Debian Bug report logs -
#744304
bind9-resolvconf.service immediately stopped after starting
Reported by: Andreas Fleig <an@zentrale1.com>
Date: Sat, 12 Apr 2014 17:45:01 UTC
Severity: important
Found in version bind9/1:9.9.5.dfsg-3
Fixed in version 1:9.10.3.dfsg.P4-12.3
Done: Ondřej Surý <ondrej@sury.org>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, andreasfleig@gmail.com, LaMont Jones <lamont@debian.org>:
Bug#744304; Package bind9.
(Sat, 12 Apr 2014 17:45:06 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Fleig <an@zentrale1.com>:
New Bug report received and forwarded. Copy sent to andreasfleig@gmail.com, LaMont Jones <lamont@debian.org>.
(Sat, 12 Apr 2014 17:45:06 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: bind9
Version: 1:9.9.5.dfsg-3
Severity: minor
Dear Maintainer,
the systemd service file "bind9-resolvconf.service" in *sid*, which I am using
in my wheezy installation (with systemd 204 from backports), is missing the
directive "RemainAfterExit=yes" in the service section. RemainAfterExit tells
systemd that a service should be considered running even after it exited.
Currently, systemd thinks the service went inactive after the ExecStart command
exits, and then immediately calls the ExecStop command, thus removing 127.0.0.1
from resolvconf.
* What led up to the situation?
The systemd service file "bind9-resolvconf.service" in *sid*, which I am using
in my wheezy installation with systemd 204 from backports, is missing the
directive "RemainAfterExit=yes" in the service section. RemainAfterExit tells
systemd that a service should be considered running even after it exited.
* What exactly did you do (or not do) that was effective (or
ineffective)?
systemctl start bind9-resolvconf.service
* What was the outcome of this action?
1. systemd runs ExecStart:
/bin/sh -c 'echo nameserver 127.0.0.1 | /sbin/resolvconf -a lo.named'
/etc/resolv.conf now contains 127.0.0.1
2. /bin/sh exits, and systemd thinks that bind9-resolvconf went inactive
3. systemd calls ExecStop:
/sbin/resolvconf -d lo.named
127.0.0.1 is removed from /etc/resolv.conf again
* What outcome did you expect instead?
127.0.0.1 should stay in /etc/resolv.conf
-- System Information:
Debian Release: 7.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bind9 depends on:
ii adduser 3.113+nmu3
ii bind9utils 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii debconf [debconf-2.0] 1.5.49
ii libbind9-80 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii libc6 2.13-38+deb7u1
ii libcap2 1:2.22-1.2
ii libdns88 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u1
ii libisc84 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii libisccc80 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii libisccfg82 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii liblwres80 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii libssl1.0.0 1.0.1e-2+deb7u6
ii libxml2 2.8.0+dfsg1-7+nmu2
ii lsb-base 4.1+Debian8+deb7u1
ii net-tools 1.60-24.2
ii netbase 5.0
bind9 recommends no packages.
Versions of packages bind9 suggests:
pn bind9-doc <none>
ii dnsutils 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii resolvconf 1.67
ii ufw 0.31.1-2
-- Configuration Files:
/etc/bind/named.conf.local changed [not included]
-- debconf information excluded
Information forwarded
to debian-bugs-dist@lists.debian.org, LaMont Jones <lamont@debian.org>:
Bug#744304; Package bind9.
(Mon, 19 Jan 2015 12:09:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Marc Haber <mh+debian-packages@zugschlus.de>:
Extra info received and forwarded to list. Copy sent to LaMont Jones <lamont@debian.org>.
(Mon, 19 Jan 2015 12:09:09 GMT) (full text, mbox, link).
Message #10 received at 744304@bugs.debian.org (full text, mbox, reply):
I can confirm both the bug and the fix in current sid in January 2015,
nine months after this bug was filed.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Information forwarded
to debian-bugs-dist@lists.debian.org, LaMont Jones <lamont@debian.org>:
Bug#744304; Package bind9.
(Fri, 13 Feb 2015 09:39:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Frederik Himpe <frederik@frehi.be>:
Extra info received and forwarded to list. Copy sent to LaMont Jones <lamont@debian.org>.
(Fri, 13 Feb 2015 09:39:04 GMT) (full text, mbox, link).
Message #15 received at 744304@bugs.debian.org (full text, mbox, reply):
Can this easy fix be applied before jessie release please?
--
Frederik Himpe <frederik@frehi.be>
Information forwarded
to debian-bugs-dist@lists.debian.org, LaMont Jones <lamont@debian.org>:
Bug#744304; Package bind9.
(Tue, 05 May 2015 23:27:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Declercq Laurent <l.declercq@nuxwin.com>:
Extra info received and forwarded to list. Copy sent to LaMont Jones <lamont@debian.org>.
(Tue, 05 May 2015 23:27:04 GMT) (full text, mbox, link).
Message #20 received at 744304@bugs.debian.org (full text, mbox, reply):
This bug is still present in Bind9 package that is provided in Jessie...
Two things:
- That would be awesome if that bug could be fixed (even for Jessie)
since it breaks systems which rely on resolvconf to setup their local
resolver.
- This service is not enabled by default, whatever the value of the
/etc/default/bind9 conffile file which defines the RESOLVCONF parameter.
I see a BC break there (or should we consider that parameters from
/etc/default are sysvinit scripts specific?)
Due to this bug, we had to work around in our control panel installer
as follow:
#################
my $serviceMngr = iMSCP::Service->getInstance();
if($service->isSystemd() && -f
'/lib/systemd/system/bind9-resolvconf.service') {
if($self->{'config'}->{'LOCAL_DNS_RESOLVER'} eq 'yes') {
# Work around #IP-1333 ( related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744304 )
# Note: This systemd system service units file is provided by
bind9 package
my $file = iMSCP::File->new( filename =>
'/lib/systemd/system/bind9-resolvconf.service' );
my $fileContent = $file->get();
unless(defined $fileContent) {
error(sprintf('Unable to read %s', $file->{'filename'}));
return 1;
} elsif($fileContent !~ /RemainAfterExit=yes/) {
$fileContent =~ s%(ExecStop=/sbin/resolvconf -d
lo.named\n)%$1RemainAfterExit=yes%;
$rs = $file->set($fileContent);
$rs ||= $file->save();
return $rs if $rs;
}
$serviceMngr->enable('bind9-resolvconf');
} else {
$serviceMngr->disable('bind9-resolvconf');
}
}
#################
That is a lot of work only for a missing option.
Thanks you.
--
Laurent Declercq
iHMS/i-MSCP Project Lead
Information forwarded
to debian-bugs-dist@lists.debian.org, LaMont Jones <lamont@debian.org>:
Bug#744304; Package bind9.
(Tue, 07 Jul 2015 04:15:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Steven Ihde <steve@x2.hamachi.us>:
Extra info received and forwarded to list. Copy sent to LaMont Jones <lamont@debian.org>.
(Tue, 07 Jul 2015 04:15:04 GMT) (full text, mbox, link).
Message #25 received at 744304@bugs.debian.org (full text, mbox, reply):
control: severity -1 important
This is a significant regression for Jessie. If the admin relied on RESOLVCONF=yes in /etc/default/bind9, the host will lose access to all names provided by the local named. This could cause any number of failures depending on the nature of the dependency. Please consider fixing this in Jessie ASAP.
Thanks,
Steve
Severity set to 'important' from 'minor'
Request was from Steven Ihde <steve@x2.hamachi.us>
to 744304-submit@bugs.debian.org.
(Tue, 07 Jul 2015 04:15:04 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, LaMont Jones <lamont@debian.org>:
Bug#744304; Package bind9.
(Tue, 23 Feb 2016 13:00:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Mario Lipinski <mario.lipinski@iserv.eu>:
Extra info received and forwarded to list. Copy sent to LaMont Jones <lamont@debian.org>.
(Tue, 23 Feb 2016 13:00:03 GMT) (full text, mbox, link).
Message #32 received at 744304@bugs.debian.org (full text, mbox, reply):
Hi,
I agree that upgrading to Jessie and thus switching to systemd results
in a BC break for RESOLVCONF=yes in /etc/default/bind9. Proper migration
should be ensured by Debian package scripts by enabling bind9-resolvconf
service for RESOLVCONF=yes.
I am surprised that a two year old bug that already has the fix in its
description did not get fixed for Jessie.
For upgrade-safe local fixes I would suggest placing a drop-in for
systemd in
/etc/systemd/system/bind9-resolvconf.service.d/fix-744304.conf
# systemd drop-in for bind9-resolvconf.service
# Fix for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744304
#
[Service]
RemainAfterExit=yes
--
Mit freundlichen Grüßen,
Mario Lipinski
IServ GmbH
Bültenweg 73
38106 Braunschweig
Telefon: 0531-2243666-0
Fax: 0531-2243666-9
E-Mail: info@iserv.eu
Internet: iserv.eu
USt-IdNr. DE265149425 | Amtsgericht Braunschweig | HRB 201822
Geschäftsführer: Benjamin Heindl, Jörg Ludwig
Reply sent
to Ondřej Surý <ondrej@sury.org>:
You have taken responsibility.
(Sun, 22 Oct 2017 11:29:50 GMT) (full text, mbox, link).
Notification sent
to Andreas Fleig <an@zentrale1.com>:
Bug acknowledged by developer.
(Sun, 22 Oct 2017 11:29:50 GMT) (full text, mbox, link).
Message #37 received at 744304-done@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Version: 1:9.10.3.dfsg.P4-12.3
Hi,
the bind9 bug list grew too much and the Debian BIND team cannot
simply test all the reported bugs against versions not in stable, so
this is mass bug close, as either the version is no longer relevant
(because of old-old-stable 9.8.x or old-stable 9.9.5 or even older
version of bind9) or the bug was already fixed.
However, if you can reproduce the bug with a current version in stable,
please use Debian BTS 'found <bug> <version_you_reproduced_the_issue>'
command to retag the bug and reopen it.
Cheers,
Ondrej
[signature.asc (application/pgp-signature, attachment)]
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Mon, 20 Nov 2017 07:25:55 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Sat Jan 6 14:54:57 2018;
Machine Name:
beach
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.