From: Attila Lendvai <attila@lendvai.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: shepherd: failing test: should `herd stop` stop a respawning process?
Date: Fri, 22 Nov 2024 20:43:41 +0000 [thread overview]
Message-ID: <wkZLkllEwNfE_0mHaxcu-Yk_KJ-f0Wv5aVHV8yZzsXdBxMrqSpYADJwXHKcXETnVvyjRioLT_wc8Pp7_tPn_-tEHhyS7ZgKpY-OpbsvndHM=@lendvai.name> (raw)
In-Reply-To: <87bjza4mee.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
> But I don’t know, there could be a bug. Could you come up with a
> reduced test case (I looked at the one attached but I’m not sure which
> part to focus on), or do you have logs of the problem?
ok, i've attached a stipped down version of the test case. it hopefully reproduces the same situation i'm observing on my servers.
which seems to be the following:
1. i have a service that keeps respawning (typically due to a config
mistake)
2. said service is upgraded/replaced in a `guix system reconfigure`
3. v1 of the service keeps respawning forever, and there's nothing i
can do to stop it at this point. `herd disable` operates on v2 of
the service, while some fiber, or some signal handler of v1 is
still in a respawn loop.
HTH,
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Our scientific power has outrun our spiritual power. We have guided missiles and misguided men.”
— Martin Luther King, Jr. (1929–1968, assassinated)
[-- Attachment #2: respawn2.sh --]
[-- Type: application/x-shellscript, Size: 3618 bytes --]
prev parent reply other threads:[~2024-11-22 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 17:02 shepherd: failing test: should `herd stop` stop a respawning process? Attila Lendvai
2024-10-06 17:31 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-10-23 20:03 ` Ludovic Courtès
2024-11-22 20:43 ` Attila Lendvai [this message]
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='wkZLkllEwNfE_0mHaxcu-Yk_KJ-f0Wv5aVHV8yZzsXdBxMrqSpYADJwXHKcXETnVvyjRioLT_wc8Pp7_tPn_-tEHhyS7ZgKpY-OpbsvndHM=@lendvai.name' \
--to=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.