Subject: bug#65419: [Shepherd] Non-reponding service control fiber

From: Ludovic Courtès <[email-masked]>
Date: Thu, 24 Aug 2023 10:09:02 +0200

Hi,

Giovanni Biscuolo <[email-masked]> 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’.