unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vladilen Kozin <vladilen.kozin@gmail.com>
To: guix-devel@gnu.org
Subject: herd stop hangs
Date: Wed, 12 Apr 2023 17:40:39 +0100	[thread overview]
Message-ID: <CACw=CXPG8V0P8i-7OngrKQ8WdhT4-mMx5fyOiOT3FPFi+BQp6w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

Hello.

I wrote a shepherd service that runs a java application in a semi standard
fashion

(start
  #~(make-forkexec-constructor ...
    #:user ..
    #:group ..
    #:environment-variables ...
(stop
  #~(make-kill-destructor)

$ sudo herd start my-service
starts without a hitch, but

$ sudo stop my-service
simply hangs for the default 5sec until Shepherd SIGKILLs it (as per
/var/log/messages) and even after that console where I run the herd stop
command doesn't get released until I manually CTRL-C it.

Been driving me nuts, cause Java handles SIGTERM but just in case I even
added shutdownHook to my app that should explicitly execute on SIGTERM and
other such signals. Testing it on OSX e.g. works just fine. But stop
wouldn't work on guix. I then decided to try everything manually:

$ start my java app from the console

In another console
$ sudo pkill -TERM pid

and nada ... it's like signal isn't even delivered.
$ sudo pkill -KILL pid

Eh ... still nothing
$ sudo kill -s SIGTERM pid
gets delivered

Ha? kill vs pkill ... ha? Could this give a clue as to why sudo herd stop
won't work?
What is going on here? Any ideas? I'm completely lost at this point.
-- 
Best regards
Vlad Kozin

[-- Attachment #2: Type: text/html, Size: 3952 bytes --]

             reply	other threads:[~2023-04-12 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 16:40 Vladilen Kozin [this message]
2023-04-12 20:05 ` herd stop hangs 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

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACw=CXPG8V0P8i-7OngrKQ8WdhT4-mMx5fyOiOT3FPFi+BQp6w@mail.gmail.com' \
    --to=vladilen.kozin@gmail.com \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).