GNU bug report logs - #64008
shepherd respawns a service even when it's disabled

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Attila Lendvai <attila <at> lendvai.name>
Subject: bug#64008: closed (Re: bug#64008: shepherd respawns a service
 even when it's disabled)
Date: Wed, 14 Jun 2023 16:50:01 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#64008: shepherd respawns a service even when it's disabled

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 64008 <at> debbugs.gnu.org.

-- 
64008: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64008
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Attila Lendvai <attila <at> lendvai.name>
Cc: 64008-done <at> debbugs.gnu.org
Subject: Re: bug#64008: shepherd respawns a service even when it's disabled
Date: Wed, 14 Jun 2023 18:49:44 +0200

Hi Attila,

Attila Lendvai <attila <at> lendvai.name> skribis:

> i'm in a situation where my service quits after a few seconds of CPU usage (i.e. the default-respawn-limit is not triggered). therefore shepherd keeps restarting it, practically in a busy loop.
>
> suggested solution:
>
> maybe respawn-service should check for the disabled state, so that the admin can intervene by `herd disable myservice`.

Turns out the service controller was ignoring the ‘enabled?’  flag,
leaving it up to the caller to check it.

This is fixed by Shepherd commit
7c88d67076a0bb1d9014b3bc23ed9c68f1c702ab.

Thanks again,
Ludo’.

[Message part 3 (message/rfc822, inline)]

From: Attila Lendvai <attila <at> lendvai.name>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: shepherd respawns a service even when it's disabled
Date: Sun, 11 Jun 2023 18:01:24 +0000

the issue:

i'm in a situation where my service quits after a few seconds of CPU usage (i.e. the default-respawn-limit is not triggered). therefore shepherd keeps restarting it, practically in a busy loop.

suggested solution:

maybe respawn-service should check for the disabled state, so that the admin can intervene by `herd disable myservice`.

a longer term solution could be to add a respawn-delay field for <service>, and default it to something non-zero.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
The mind: an excellent servant, but a dangerous master.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.