From: Alex Efros <powerman@powerman.name>
To: supervision@list.skarnet.org
Subject: Re: runit-1.8.0 available
Date: Sat, 20 Oct 2007 22:59:50 +0300 [thread overview]
Message-ID: <20071020195950.GB25023@home.power> (raw)
In-Reply-To: <20071016033818.GE18461@run.duo>
Hi!
On Mon, Oct 15, 2007 at 11:38:18PM -0400, George Georgalis wrote:
> This thread(s) is so long it's become difficult to follow. Maybe
> you could consolidate the important details into a summary. What
> is the simplest way to reproduce the problem. What has been tried?
> What factors are determined not related. What hypothesis, if any,
> for resolution?
Only known to me way to reproduce the problem - install new Gentoo server
and wait for about a week to see sshd zombies (as result of ssh-worms
trying to bruteforce ssh from time to time).
Tried? I tried to switch from runit-init to sysvinit, and this solved issue.
Also Gerrit suggested a workaround: running 'chmod -x /etc/runit/stopit;
kill -CONT 1' on system with unreaped zombies result in two things: first
all zombies are reaped, and second runit start reaping zombies again...
but after several days it stop reaping zombies again and we need to
chmod/kill again.
Not related... there several factors determined not related (like
grsecurity kernel patches), but that was while I wasn't sure this is bug
in runit.
Mostly strange thing is this happens as least for two people, at same time
after Gentoo upgrade. And that upgrade doesn't touch runit or toolchain -
nothing in this upgrade seems suspicious.
Only hypothesis I've - this issue related to date/time: it usually happens
at same time on all my servers (and looks like this related to global
date/time, and not to server uptime), and it usually repeats every 5-7 days.
I think easies way to solve this issue - if Gerrit provide test/debug
version of runit to me, which for example output it state/actions into log
file, and then he'll analyse that log file to find out what is going wrong.
Because looks like he unable to find this bug by just looking at the code.
--
WBR, Alex.
next prev parent reply other threads:[~2007-10-20 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 11:12 Gerrit Pape
2007-09-21 12:30 ` Alex Efros
2007-09-22 14:37 ` Alex Efros
2007-09-24 10:19 ` Gerrit Pape
2007-09-24 13:35 ` Alex Efros
2007-09-26 13:46 ` Alex Efros
2007-09-29 13:00 ` Alex Efros
2007-09-29 13:03 ` Alex Efros
2007-09-29 13:21 ` Alex Efros
2007-10-06 5:49 ` Alex Efros
2007-10-11 12:53 ` Gerrit Pape
2007-10-13 17:30 ` Alex Efros
2007-10-20 11:24 ` Alex Efros
2007-10-13 21:27 ` Alex Efros
2007-10-16 3:38 ` George Georgalis
2007-10-20 19:59 ` Alex Efros [this message]
2007-10-20 22:11 ` George Georgalis
2007-10-20 22:20 ` Alex Efros
2007-10-22 22:17 ` Vincent Danen
2007-10-24 3:52 ` George Georgalis
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=20071020195950.GB25023@home.power \
--to=powerman@powerman.name \
--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).