[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



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

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: