supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Yoshinori Sato <yo-satoh@sios.com>
To: supervision@list.skarnet.org
Subject: runit don't restart service.
Date: Wed, 25 Jul 2018 15:29:25 +0900	[thread overview]
Message-ID: <CAL_XjKV6FDzg4-fv8K2c0pgSKFbo0zhA9DJ_gKQ4aHE_vSymKQ@mail.gmail.com> (raw)

Hello.

I'm using runit-2.1.2. I have a question about this.

I checked the operation at the time of service abnormality.

- before problem.
[root@nodeA ec2-user]# ps -ewwwf |grep lkcheck
root     10647 10592  0 7月13 ?  00:00:00 /opt/LifeKeeper/sbin/runsv lkcheck
root     12521 10647  0 7月13 ?  00:00:02 /opt/LifeKeeper/bin/lkcheck
root     12523 12521  0 7月13 ?  00:00:00 /opt/LifeKeeper/bin/lklogmsg
-p lkcheck -l LK_ERROR -s runit -t  -a uncaught_error -i 0 -c
/opt/LifeKeeper/bin/lkcheck
root     25993 23089  0 02:19 pts/0    00:00:00 grep --color=auto lkcheck

lkcheck is runit managed service process.

- terminate service
[root@nodeA ec2-user]# kill 10647 12521

- restart check
[root@nodeA ec2-user]# ps -ewwwf |grep lkcheck
root     26053 10592  0 02:20 ?        00:00:00
/opt/LifeKeeper/sbin/runsv lkcheck
root     26056 23089  0 02:20 pts/0    00:00:00 grep --color=auto lkcheck

I was hoping that lkcheck was restarting.
However, it has not restarted.

I would like to know if this behavior is a specification.

Thanks.


             reply	other threads:[~2018-07-25  6:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25  6:29 Yoshinori Sato [this message]
2018-07-25  8:35 ` Jonathan de Boyne Pollard
2018-07-25  8:53   ` Yoshinori Sato

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=CAL_XjKV6FDzg4-fv8K2c0pgSKFbo0zhA9DJ_gKQ4aHE_vSymKQ@mail.gmail.com \
    --to=yo-satoh@sios.com \
    --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).