[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#62163: Suppress logging shepherd evaluation in mcron.log
From: |
Bruno Victal |
Subject: |
bug#62163: Suppress logging shepherd evaluation in mcron.log |
Date: |
Thu, 30 Mar 2023 12:21:18 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 |
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.
>
> You can send messages to the bitbucket with:
>
> (parameterize ((shepherd-message-port (%make-void-port "w0")))
> …)
Thanks!
I'm still curious as to exactly what/which lines cause shepherd to output the
lines.
Cheers,
Bruno