all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vlad Kozin <vladilen.kozin@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: herd stop hangs
Date: Mon, 17 Apr 2023 15:41:38 +0200	[thread overview]
Message-ID: <87fs8yeict.fsf@gnu.org> (raw)
In-Reply-To: <80A65A09-697F-444B-9E53-72D9088C57EB@gmail.com> (Vlad Kozin's message of "Thu, 13 Apr 2023 22:02:27 +0100")

Hi,

Vlad Kozin <vladilen.kozin@gmail.com> skribis:

>> (I guess the second command is ‘sudo herd stop my-service’.)  If you
>> interrupt the ‘herd’ command, does ‘sudo herd status’ and similar
>> commands still respond?
>
> ‘sudo herd stop myservice’ exactly. Sorry about that.
> Herd continues to function. Appears that somehow SIGTERM has no effect
> or it never gets sent or it is in fact delivered and acted upon but
> shepherd fails to notice, so /var/log/messages shows subsequent
> SIGKILL. Whichever it is, herd status will show the service has been
> stopped. That’s one issue.

Could you send the relevant /var/log/messages excerpt?

How frequent is it?  If you have a recipe to reproduce the issue, I’m
most interested!

> Another is that the console where ‘sudo herd stop’ was typed required
> a CTRL C to get the prompt.

OK.

> Could it be some weird sequence of what appears in the :running slot or smth? I’m using standard process constructors destructors mimicking other services

If this is a service that’s not in Guix proper, could you share the
code?  That way we’ll have everything we need to investigate.

Thanks,
Ludo’.


      reply	other threads:[~2023-04-17 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 16:40 herd stop hangs Vladilen Kozin
2023-04-12 20:05 ` Attila Lendvai
2023-04-12 22:04   ` Vlad Kozin
2023-04-13  3:59 ` Ivan Sokolov
2023-04-13 20:04 ` Ludovic Courtès
2023-04-13 21:02   ` Vlad Kozin
2023-04-17 13:41     ` Ludovic Courtès [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=87fs8yeict.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=vladilen.kozin@gmail.com \
    /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.