From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 41429@debbugs.gnu.org
Subject: bug#41429: Shepherd Sometimes Crashes
Date: Thu, 21 May 2020 07:51:54 -0500 [thread overview]
Message-ID: <87sgftbgd1.fsf@gmail.com> (raw)
In-Reply-To: <20200521121443.GC958@E5400> (Efraim Flashner's message of "Thu, 21 May 2020 15:14:43 +0300")
Efraim Flashner <efraim@flashner.co.il> writes:
> On Wed, May 20, 2020 at 09:59:03PM -0500, Katherine Cox-Buday wrote:
>> I am running shepherd as a userspace service manager on an alien distro.
>> Occassionally (often enough as to cause concern), Shepherd is crashing.
>> I am unable to narrow down a cause, but anecdotally, it seems to happen
>> more often when a service it's managing fails repeatedly and is
>> disabled.
>>
>> I'm running `strace` against the Shepherd process in an attempt to
>> submit a better bug report, but this is all I have for now. Maybe others
>> have also seen this behavior.
>
> I found it happens less often with shepherd-0.8. What version are you
> running? Also possibly related, do you have mismatched versions of guile
> between guix packages and your distro's native packages?
Sorry, I forgot to include the version! I am running 0.8 from a store
which I update ~1 week.
> I've also sometimes found shepherd to crash when I add a service where
> the start command is "wrong", as though the error were so bad that
> shepherd says "Nope! That's it! I quit!"
I'm doing very standard things with `make-forkexec-constructor`, so I
wouldn't expect any problems there.
Your comment is kind of scary though! Shepherd is the thing I want to
stay up no matter what since it's responsible for monitoring and
restarting things. The idea that a misbehaving or poorly written service
could bring down the entire Shepherd process is a problem! Is there no
isolation?
> I'd suggest looking at .config/shepherd/shepherd.log but it's rather
> sparse. Still, it might have something useful.
Yes, this is the first place I looked, but unfortunately there wasn't
much usable informatino.
--
Katherine
next prev parent reply other threads:[~2020-05-21 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 2:59 bug#41429: Shepherd Sometimes Crashes Katherine Cox-Buday
2020-05-21 12:14 ` Efraim Flashner
2020-05-21 12:51 ` Katherine Cox-Buday [this message]
2020-05-21 14:04 ` Efraim Flashner
2020-05-21 15:59 ` Katherine Cox-Buday
2020-05-22 17:39 ` Mathieu Othacehe
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=87sgftbgd1.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=41429@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).