From: Colin Booth <colin@heliocat.net>
To: supervision@list.skarnet.org
Subject: Re: "Back off" setting for crashing services with s6+openrc?
Date: Mon, 26 Sep 2022 23:00:48 +0000 [thread overview]
Message-ID: <YzIvIOpcJ4gxvt7d@cathexis.xen.prgmr.com> (raw)
In-Reply-To: <CAPhAwGymgEyYzSFbhV3ozAfjEUwgWW2Wzd_QO9Se7Ozw8=wnDQ@mail.gmail.com>
On Thu, Sep 22, 2022 at 01:21:46PM -0700, John W Higgins wrote:
> Good Day,
>
> On Thu, Sep 22, 2022 at 1:13 PM Tor Rune Skoglund <trs@fourc.eu> wrote:
> ...
>
> > As a generic question, is there any setting with this s6+openrc config
> > that would make s6 "back off" a configurable number of seconds before
> > doing the restart?
> >
> >
> Does something as simple as changing your run script to be something like
>
> run_my_crashing_app || sleep 10
>
> Work? The run script will sit there for 10 seconds if your app fails. Not
> built in - but should accomplish the task pretty easily.
>
> John W Higgins
Put the backoff in the finish script. The API is to run finish with the
exit code and signal (if appropriate) as $1 and $2 respectively. With
that information you can have finish make decisions about if it should
delay restarting, set the service down in the face of a permanent error,
or so on. Note that by default finish has a five second deadline so if
you want to delay a restart for ten seconds you'll need to increase that
deadline with a timeout-finish file.
--
Colin Booth
next prev parent reply other threads:[~2022-09-26 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 19:45 Tor Rune Skoglund
2022-09-22 20:21 ` John W Higgins
2022-09-23 7:29 ` Tor Rune Skoglund
2022-09-23 16:44 ` Alyssa Ross
2022-09-24 12:33 ` Oliver Schad
2022-09-26 23:00 ` Colin Booth [this message]
2022-09-30 9:34 ` Oliver Schad
2022-09-30 13:21 ` Laurent Bercot
2022-10-04 14:16 ` Tor Rune Skoglund
2022-10-10 16:20 ` Laurent Bercot
2022-10-11 0:38 ` Dewayne
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=YzIvIOpcJ4gxvt7d@cathexis.xen.prgmr.com \
--to=colin@heliocat.net \
--cc=supervision@list.skarnet.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.
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 NNTP newsgroup(s).