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 10:59:43 -0500 [thread overview]
Message-ID: <87k115b7o0.fsf@gmail.com> (raw)
In-Reply-To: <20200521140442.GF958@E5400> (Efraim Flashner's message of "Thu, 21 May 2020 17:04:42 +0300")
Efraim Flashner <efraim@flashner.co.il> writes:
>> 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 have a whole collection of attempts to integrate mcron with shepherd,
> to create loops and add jobs only when the service is active. Attempting
> to fork off and then collect the child process and then fail just enough
> to make the service restart. Lots of cringe-worthy code. The more common
> fail scenarios I see are shepherd fails to start because it doesn't like
> my start code of one of the services or actually starting the service
> somehow kills it. All of those were with straight lambdas to the start
> command though.
I'm not familiar with Shepherd's internals, so I don't know why
interacting with a cron is relevant.
> Do you have your services writing out any logs? Maybe there's a clue
> there.
Not yet, but I should be enabling this soon, and if they display
anything I'll report back.
Still, this seems beside the point: the bug is that Shepherd needs to
stay up regardless of what the services it's monitoring do.
--
Katherine
next prev parent reply other threads:[~2020-05-21 16:01 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
2020-05-21 14:04 ` Efraim Flashner
2020-05-21 15:59 ` Katherine Cox-Buday [this message]
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=87k115b7o0.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).