From: Giovanni Biscuolo <g@xelera.eu>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>, 65419@debbugs.gnu.org
Cc: Christopher Baines <mail@cbaines.net>
Subject: bug#65419: [Shepherd] Non-reponding service control fiber
Date: Wed, 23 Aug 2023 10:00:15 +0200 [thread overview]
Message-ID: <87pm3ejii8.fsf@xelera.eu> (raw)
In-Reply-To: <87il98burf.fsf@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Hello,
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
[...]
> The conclusion seems to be that the control fiber of the ‘root’ service
> is not responding: it is blocked on a get/put? did it exit?
>
> Unfortunately we don’t have data from the logs that would give clues as
> to what went wrong.
I've had a look at /var/log/messages but nothing seems wrong except
messages like this one:
--8<---------------cut here---------------start------------->8---
Aug 21 14:48:42 localhost shepherd[1]: 6 connections still in use after sshd-13752 termination.
Aug 21 14:48:42 localhost shepherd[1]: Service sshd-13752 (PID 29977) exited with 255.
Aug 21 14:48:42 localhost shepherd[1]: Service sshd-13752 has been disabled.
Aug 21 14:48:42 localhost shepherd[1]: Transient service sshd-13752 terminated, now unregistered.
--8<---------------cut here---------------end--------------->8---
Is it useful configuring the monitoring service [1] on milano-guix-1 to
have useful data in the logs in case we get a similar issue?
Thanks, Gio'
[1] https://www.gnu.org/software/shepherd/manual/shepherd.html#Monitoring-Service
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2023-08-23 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 9:38 bug#65419: [Shepherd] Non-reponding service control fiber Ludovic Courtès
2023-08-23 8:00 ` Giovanni Biscuolo [this message]
2023-08-24 8:09 ` 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=87pm3ejii8.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=65419@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=mail@cbaines.net \
/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).