[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65419: [Shepherd] Non-reponding service control fiber
From: |
Giovanni Biscuolo |
Subject: |
bug#65419: [Shepherd] Non-reponding service control fiber |
Date: |
Wed, 23 Aug 2023 10:00:15 +0200 |
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
signature.asc
Description: PGP signature