On 2017-09-22 09:49:16 +0200, Vincent Lefevre wrote:
> I've attached the part of the journalctl output that occurred during
> the upgrade. This may be more useful. In particular, the following
> looks strange:
>
> [...]
> Sep 21 10:21:56 zira avahi-daemon[740]: avahi-daemon 0.6.32 exiting.
> Sep 21 10:21:56 zira systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
> Sep 21 10:21:56 zira systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
> Sep 21 10:21:56 zira avahi-daemon[740]: Daemon already running on PID 740
> [...]
>
> Why the "Daemon already running on PID 740" if it has stopped
> as said two lines above?
The only thing I could find related to a stopping issue is:
avahi (0.7-2) unstable; urgency=medium
[...]
* Handle socket activation in avahi-daemon-check-dns.sh when using systemd.
To completely stop avahi-daemon under systemd the avahi-daemon.socket
unit needs to be stopped as well. (Closes: #847456)
-- Michael Biebl <bi...@debian.org> Sun, 17 Sep 2017 23:43:27 +0200
Could this be related? Note that the previous version in my case was
a 0.6.32, so that it was affected by this bug.
If this is the case, and even if the bug is in 0.6.32, I suppose
that something needs to be done in order to avoid a possible
upgrade failure as I got.
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
