unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: 65419@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>
Subject: bug#65419: [Shepherd] Non-reponding service control fiber
Date: Thu, 24 Aug 2023 10:09:02 +0200	[thread overview]
Message-ID: <87jztk276p.fsf@inria.fr> (raw)
In-Reply-To: <87pm3ejii8.fsf@xelera.eu> (Giovanni Biscuolo's message of "Wed,  23 Aug 2023 10:00:15 +0200")

Hi,

Giovanni Biscuolo <g@xelera.eu> skribis:

> I've had a look at /var/log/messages but nothing seems wrong except
> messages like this one:
>
>
> 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. 

Yeah, I think it happened earlier but unfortunately the previously logs
got deleted (rottlog is not behaving as expected).

> 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?

It wouldn’t help in this case, but it’s still interesting to have it
around.

  sudo herd eval root '(begin (use-modules (shepherd service monitoring)) (register-services (list (monitoring-service))))'
  sudo herd start monitoring

Ludo’.




      reply	other threads:[~2023-08-24  8:10 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
2023-08-24  8:09   ` Ludovic Courtès [this message]

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=87jztk276p.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=65419@debbugs.gnu.org \
    --cc=g@xelera.eu \
    --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).