Bug#989284: insserv: toggles rc0.d/{K02avahi-daemon => K01avahi-daemon} with every upgrade

[Jesse Smith]

On 2021-09-26 1:54 p.m., Thorsten Glaser wrote:
> On Sun, 26 Sep 2021, Jesse Smith wrote:
>
>> Something that might be useful here is seeing the output from "insserv
>> -v -s -n". This will show in what order insserv intends to assign each
>> service in each runlevel. No changes will be made to the system when
>> insserv is run with the "-n" flag.
> Attached.
>
>> It might also be useful to have the LSB header from the avahi-daemon
>> service file in /etc/init.d/
> root at tglase:/etc # head -15 /etc/init.d/avahi-daemon  
> #!/bin/sh
> ### BEGIN INIT INFO
> # Provides:          avahi avahi-daemon
> # Required-Start:    $remote_fs dbus
> # Required-Stop:     $remote_fs dbus
> # Should-Start:      $syslog
> # Should-Stop:       $syslog
> # Default-Start:     2 3 4 5
> # Default-Stop:      0 1 6
> # Short-Description: Avahi mDNS/DNS-SD Daemon
> # Description:       Zeroconf daemon for configuring your network 
> #                    automatically
> ### END INIT INFO
>
> PATH=/sbin:/bin:/usr/sbin:/usr/bin
>

Thanks, Thorseten, this is very helpful. So if I understand correctly if
you do the "apt upgrade" process now (or a regular insserv call)
avahi-daemon will get set to K01. Which looks right to me. But then if
you run insserv a second time it toggles back to K02?

Could you try this for me? Send me the same style of recored output you
did last time. This time please run"

# insserv -v -s

This should set avahi-daemon to K01. Then run

# insserv -v -s -n

This should tell us whether insserv wants to toggle avahi-daemon back to
K02, but without actually making any changes. And hopefully it will give
a clue as to why this is happening.Thank you.

- Jesse