From: "Ludovic Courtès" <ludo@gnu.org>
To: 72670@debbugs.gnu.org
Subject: bug#72670: avahi-daemon can fail to restart due to stale /run/avahi-daemon/pid
Date: Fri, 16 Aug 2024 15:32:29 +0200 [thread overview]
Message-ID: <877ccg8ufm.fsf@inria.fr> (raw)
The ‘avahi-daemon’ service fails to restart these days: a stale
/run/avahi-daemon/pid upon reboot leads it to abandon. From
/var/log/messages:
--8<---------------cut here---------------start------------->8---
Aug 16 13:29:11 localhost shepherd[1]: Starting service avahi-daemon...
Aug 16 13:29:11 localhost shepherd[1]: Service avahi-daemon has been started.
Aug 16 13:29:11 localhost shepherd[1]: Service avahi-daemon started.
Aug 16 13:29:11 localhost shepherd[1]: Service avahi-daemon running with value (("unknown" . #<input-output: socket 27>)).
Aug 16 13:29:11 localhost shepherd[1]: Spawning systemd-style service /gnu/store/yfl1x5k3njghkg4ckximqb0ysppvx8na-avahi-0.8/sbin/avahi-daemon.
Aug 16 13:29:11 localhost shepherd[1]: Running value of service avahi-daemon changed to 1497.
Aug 16 13:29:11 localhost shepherd[1]: Service avahi-daemon (PID 1497) exited with 255.
Aug 16 13:29:11 localhost shepherd[1]: Service avahi-daemon has been disabled.
Aug 16 13:29:11 localhost shepherd[1]: (Respawning too fast.)
--8<---------------cut here---------------end--------------->8---
… and /var/log/avahi-daemon.log:
--8<---------------cut here---------------start------------->8---
2024-08-16 13:29:11 Daemon already running on PID 1346
2024-08-16 13:29:11 Daemon already running on PID 1346
2024-08-16 13:29:11 Daemon already running on PID 1346
2024-08-16 13:29:11 Daemon already running on PID 1346
2024-08-16 13:29:11 Daemon already running on PID 1346
2024-08-16 13:29:11 Daemon already running on PID 1346
2024-08-16 13:29:11 Daemon already running on PID 1346
--8<---------------cut here---------------end--------------->8---
The issue was uncovered by the switch to socket activation in commit
3298ec0200af0d0b0850a388df0a78e87320307f: despite using socket
activation, avahi-daemon checks for the presence of a PID file; however,
there’s no longer a cleanup process as is the case when #:log-file is
used, hence the bug.
But the core problem seems to be that ‘cleanup-service-type’ deletes
/var/run at boot but not /run. I guess it should delete /run as well?
Ludo’.
next reply other threads:[~2024-08-16 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 13:32 Ludovic Courtès [this message]
2024-08-18 20:47 ` bug#72670: avahi-daemon can fail to restart due to stale /run/avahi-daemon/pid Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ccg8ufm.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=72670@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).