[Pkg-sysvinit-devel] [avahi-dnsconfd] fails to start at boot

[Michael Biebl]

Control: reassign -1 startpar

Hi Maurizio,

first of all, apologies for not replying earlier.

On Thu, 09 Jan 2014 13:09:38 +0100 Maurizio Avogadro <mavoga at gmail.com>
wrote:
> Package: avahi-dnsconfd
> Version: 0.6.31-4
> Severity: normal
> 
> 
> The avahi-dnsconfd daemon failed to start at boot; in the daemon.log I
> found:
> 
> [...]
> Jan  8 17:28:41 w150hrm avahi-dnsconfd[3997]: connect(): No such file or
> directory
> Jan  8 17:28:41 w150hrm avahi-dnsconfd[3997]: Failed to connect to the
> daemon. This probably means that you
> Jan  8 17:28:41 w150hrm avahi-dnsconfd[3997]: didn't start avahi-daemon
> before avahi-dnsconfd.
> [...]
> 
> The output of $ ls -1 /etc/rc?.d/*avahi* is:
> 
> /etc/rc0.d/K01avahi-dnsconfd
> /etc/rc0.d/K03avahi-daemon
> /etc/rc1.d/K01avahi-dnsconfd
> /etc/rc1.d/K03avahi-daemon
> /etc/rc2.d/S20avahi-daemon
> /etc/rc2.d/S22avahi-dnsconfd
> /etc/rc3.d/S20avahi-daemon
> /etc/rc3.d/S22avahi-dnsconfd
> /etc/rc4.d/S20avahi-daemon
> /etc/rc4.d/S22avahi-dnsconfd
> /etc/rc5.d/S20avahi-daemon
> /etc/rc5.d/S22avahi-dnsconfd
> /etc/rc6.d/K01avahi-dnsconfd
> /etc/rc6.d/K03avahi-daemon
> 
> Oddly enough, I verified that at boot avahi-dnsconfd got started
> _before_ avahi-daemon, and I begun to suspect that the init system (I'm
> using sysvinit 2.88dsf-45; please see the attached graphs of the boot
> dependencies) were getting confused because of the multiple "Provides:"
> LSB header field of the avahi-daemon init script:
> 
> [...]
> ### BEGIN INIT INFO
> # Provides:          avahi avahi-daemon
> [...]
> 
> The avahi-dnsconfd initscript currently requires "avahi-daemon":
> 
> [...]
> ### BEGIN INIT INFO
> # Provides:          avahi-dnsconfd
> # Required-Start:    $remote_fs avahi-daemon
> # Required-Stop:     $remote_fs avahi-daemon
> [...]
> 
> Making avahi-dnsconfd initscript require "avahi" instead of
> "avahi-daemon" allowed me to correctly start the daemon _after_
> avahi-daemon at boot.
> 
> Since the solution looked straight and simple, even if this could indeed
> be considered a sysvinit issue, I chose to file this bug against


So, the start priorities S22avahi-dnsconfd and S20avahi-daemon look ok.
With sysvinit, after the switch to dependency based boot, startpar is
used to start the individual services.

I assume startpar computed the wrong dependency information to compute
the services in the correct order.
Using multiple Provides shouled be fine, as documented in
https://refspecs.linuxfoundation.org/LSB_3.0.0/LSB-PDA/LSB-PDA/initscrcomconv.html

I'm thus reassigning this bug to startpar.

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20170917/bfe8a4f5/attachment.sig>