Bug#744304: bind9-resolvconf.service immediately stopped after starting

[Declercq Laurent]

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


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#744304: bind9-resolvconf.service immediately stopped after starting

[Frederik Himpe]

Can this easy fix be applied before jessie release please?


-- 
Frederik Himpe frede...@frehi.be


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#744304: bind9-resolvconf.service immediately stopped after starting

[Marc Haber]

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#744304: bind9-resolvconf.service immediately stopped after starting

[Andreas Fleig]

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  adduser3.113+nmu3
ii  bind9utils 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii  debconf [debconf-2.0]  1.5.49
ii  libbind9-801:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii  libc6  2.13-38+deb7u1
ii  libcap21: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  libisccfg821:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii  liblwres80 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii  libssl1.0.01.0.1e-2+deb7u6
ii  libxml22.8.0+dfsg1-7+nmu2
ii  lsb-base   4.1+Debian8+deb7u1
ii  net-tools  1.60-24.2
ii  netbase5.0

bind9 recommends no packages.

Versions of packages bind9 suggests:
pn  bind9-doc   none
ii  dnsutils1: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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org