From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Bruno Victal <mirai@makinata.eu>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 62163@debbugs.gnu.org
Subject: bug#62163: Suppress logging shepherd evaluation in mcron.log
Date: Thu, 30 Mar 2023 22:10:31 -0400 [thread overview]
Message-ID: <871ql5zn54.fsf@gmail.com> (raw)
In-Reply-To: <e71b366d-9002-ff25-623a-5fac660b9481@makinata.eu> (Bruno Victal's message of "Thu, 30 Mar 2023 12:21:18 +0100")
Hi,
Bruno Victal <mirai@makinata.eu> writes:
> On 2023-03-30 11:22, Ludovic Courtès wrote:
>> Hi,
>>
>> Bruno Victal <mirai@makinata.eu> skribis:
>>
>>> On 2023-03-28 17:25, Ludovic Courtès wrote:
>>>>
>>>> Nope. :-) What is ‘my-heartbeat-job’ doing?
>>>
>>> It queries shepherd to see if a service is running and sends a restart if required.
>>
>> Isn’t that what #:respawn? #t is supposed to do? :-)
>>
>> If you find that #:respawn? doesn’t work, then we should fix it.
>
> Oh, I should have explained better here.
> Re-spawn works, it's the (daemon) service that might misbehave/go unresponsive without crashing,
> i.e. HTTP backend stops responding to API requests but the server is still up.
> The job performs a "health-check" and restarts it if it doesn't get the appropriate response.
>
> A concrete situation where this could be of use is for logs.guix that occasionally stops
> recording.
So some kind of supervisor for the job, that specific run time checks to
ensure the process is still doing its job, if I understand correctly. I
wonder if this use case could be integrated into our Shepherd services
themselves, via some supervisor slot or similar, that would run some
script periodically.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-03-31 2:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 15:59 bug#62163: Suppress logging shepherd evaluation in mcron.log Bruno Victal
2023-03-24 12:22 ` Maxim Cournoyer
2023-03-28 16:25 ` Ludovic Courtès
2023-03-28 16:32 ` Bruno Victal
2023-03-30 10:22 ` Ludovic Courtès
2023-03-30 11:21 ` Bruno Victal
2023-03-31 2:10 ` Maxim Cournoyer [this message]
2023-03-31 12:18 ` Ludovic Courtès
2023-03-31 11:52 ` Bruno Victal
2023-03-31 22:10 ` Ludovic Courtès
2023-04-27 13:24 ` Ludovic Courtès
2023-04-27 16:12 ` Bruno Victal
2023-04-28 3:52 ` Maxim Cournoyer
2023-05-03 20:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871ql5zn54.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=62163@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mirai@makinata.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.