Hi,
Vlad Kozin 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 som
> (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
Hi,
Vladilen Kozin skribis:
> $ 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 unt
Vladilen Kozin writes:
> 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
Indeed reboot / shutdown no longer work … wat :)
Don’t have any bright ideas about possible next steps tbh.
Best,
Vlad
> On Apr 12, 2023, at 9:05 PM, Attila Lendvai wrote:
>
>
>>
>> What is going on here? Any ideas? I'm completely lost at this point.
>
> a random stab: with custom servic
> What is going on here? Any ideas? I'm completely lost at this point.
a random stab: with custom service code, it's possible to put shepherd into a
state where it doesn't respond to herd remote requests anymore (nor
shutdown/reboot requests). try if your shepherd works fine otherwise, e.g. with
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
