#792428 openresolv: "Failed to get D-Bus connection" randomly at update and boot on bind9 restart

Package:
openresolv
Source:
openresolv
Submitter:
Thibaut Chèze
Date:
2015-12-01 23:09:03 UTC
Severity:
normal
#792428#5
Date:
2015-07-14 17:48:58 UTC
From:
To:
After an update from any source (dhcp, openvpn, static, ...), restart of
bind fail with message:
Failed to get D-Bus connection: Operation not permitted

It's not all the time, but very very often.

Best regards,

Thibaut Chèze
#792428#10
Date:
2015-07-14 18:12:40 UTC
From:
To:
My workaround for this problem is to stay in version /3.5.2-1/.

Le 14/07/2015 19:48, Thibaut Chèze wrote :
#792428#15
Date:
2015-09-17 14:50:05 UTC
From:
To:
In openresolv, only the dnsmasq subscriber uses DBus.
All the named subscriber (bind) in openresolv will do is write the
config files and restart named (bind).

Have you modified the named subscriber to use DBus or do you write out
to a dnsmasq configuration file as well?

Please post your /etc/resolvconf.conf file.

Roy
#792428#20
Date:
2015-09-17 14:57:47 UTC
From:
To:
the named (bind) subscriber doesn't use DBus, only the dnsmasq
subscriber does.
Are you sure it's bind it's trying to restart?

Can you post your /etc/resolvconf.conf please?

Roy
#792428#25
Date:
2015-11-26 17:22:46 UTC
From:
To:
Hi,

Maybe Thibaut didn't receive the email because
he is not subscribed.

Please read below.

Bug reported 2015-07-14:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792428

 the named (bind) subscriber doesn't use DBus, only the dnsmasq
 subscriber does.
 Are you sure it's bind it's trying to restart?

 Can you post your /etc/resolvconf.conf please?

 Roy




regards,
#792428#30
Date:
2015-12-01 22:58:58 UTC
From:
To:
Hi,

Sorry about the late response, notifications seems to be failed.

/etc/resolvconf.conf:
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#name_servers=127.0.0.1
name_servers=127.0.0.1

search_domains=test

# Mirror the Debian package defaults for the below resolvers
# so that resolvconf integrates seemlessly.
#dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
#pdnsd_conf=/etc/pdnsd.conf
#unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
named_options=/var/lib/bind/resolvconf-options.conf
named_zones=/var/lib/bind/resolvconf-zones.conf


I did some tests since Thursday, with versions /3.7.0-1/, /3.7.1-1/ and
/3.7.2-1/, and I see a new message instead of the old one:
Failed to try-restart nscd.service: No such method 'TryRestartUnit'
Failed to try-restart named.service: No such method 'TryRestartUnit'


The second line appears alone some times.

These lines make me think that /systemd/ is used to reload the service,
but my configurations use /sysvinit/.
The previous version /3.5.2-1/ seems to use the init script in
//etc/init.d/ instead.

Best regards,

Thibaut Chèze