From: Charles Duffy <cduffy@spamcop.net>
Subject: runit under sysvinit - coping when runsvdir dies
Date: Mon, 14 Nov 2005 12:03:20 -0600 [thread overview]
Message-ID: <dlajh8$eqj$1@sea.gmane.org> (raw)
I recently had a situation on a fielded server where runsvdir (from
runit 1.2.3) apparently died; in any event, all the runsv processes
which would typically be directly under runsvdir were instead inherited
by sysvinit and running there. However, since runsvdir was respawned by
sysvinit, a great deal of CPU time was being spent continuously trying
to start new runsv instances under the fresh runsvdir -- attempts which
failed because there were still runsv instances alive and holding open
the relevant locks. I killed the old runsv instances with "runsvctrl e",
and fresh children of the new runsvdir took their place -- but there are
still some questions raised:
- How could this have happened? The system's message log doesn't show
the OOM killer taking down runsvdir or any segfault on the part of the same.
- How could such situations be more gracefully handled in the future?
Having the customer call and complain because their server was unusably
slow was a less-than-ideal way to find out about this issue.
next reply other threads:[~2005-11-14 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 18:03 Charles Duffy [this message]
2005-11-16 3:50 ` Charlie Brady
2005-11-17 9:08 ` Gerrit Pape
2005-11-17 11:13 ` Charles Duffy
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='dlajh8$eqj$1@sea.gmane.org' \
--to=cduffy@spamcop.net \
/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).