From: Dmitry Bogatov <KAction@debian.org>
To: Guillermo <gdiazhartusch@gmail.com>
Cc: Supervision <supervision@list.skarnet.org>, 916230-quiet@bugs.debian.org
Subject: Re: Log rotation issue with runit
Date: Sat, 29 Dec 2018 18:33:18 +0000 [thread overview]
Message-ID: <E1gdJQG-00047Z-01@eggs.gnu.org> (raw)
In-Reply-To: <CADQ2Nw-j_KsDJwV_xv_G+MEtEgwi0nihiPf=kh0M+Jy8+K0odg@mail.gmail.com>
[2018-12-27 20:39] Guillermo <gdiazhartusch@gmail.com>
> El jue., 27 dic. 2018 a las 6:36, Dmitry Bogatov escribió:
> >
> > And this issue happens not only on crash, it happens after every
> > termination of svlogd, due any signal. I would agree that SIGKILL is
> > crash, but issue reproduces with SIGINT and SIGTERM.
>
> SIGTERM should make svlogd exit cleanly, are you sure? It does for me,
> and when restarted, does not create any .u file (using Gentoo's runit,
> which is upstream runit plus a minor patch to the makefile).
Wierd. I tried again, and failed to reproduced issue with SIGTERM this
time. So seems that problem is that svlogd is killed by some other
signal. It is going to be quite a long debugging session.
> > /etc/runit/3 changed [not included]
>
> What does this mean? Is this Debian with runit as the init system and
> a modified /etc/runit/3 instead of the one supplied with the Debian
> package?
Yes.
> I'm going to make a guess here and say that the supervision tree is
> not being teared down properly, resulting in svlogd processes not
> exiting cleanly and producing lots of .u files, compounded with the
> fact that they are never deleted during rotations because of the fix
> to bug #878476...
What do you mean, `supervision tree not not being teared down properly'?
next prev parent reply other threads:[~2018-12-29 18:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 13:39 Dmitry Bogatov
2018-12-25 14:57 ` Alex Efros
2018-12-25 18:17 ` Guillermo
2018-12-25 18:30 ` Guillermo
2018-12-26 1:58 ` Alex Efros
2018-12-27 9:36 ` Dmitry Bogatov
2018-12-27 11:41 ` Laurent Bercot
2018-12-28 6:47 ` Jonathan de Boyne Pollard
2018-12-27 13:47 ` Steve Litt
2018-12-28 1:27 ` Guillermo
2018-12-27 23:39 ` Guillermo
2018-12-29 18:33 ` Dmitry Bogatov [this message]
2018-12-29 22:32 ` Guillermo
2018-12-28 6:57 ` Jonathan de Boyne Pollard
2018-12-26 5:05 ` Steve Litt
2018-12-27 9:36 ` Dmitry Bogatov
2018-12-27 13:07 ` Steve Litt
2018-12-29 18:33 ` Dmitry Bogatov
2018-12-30 1:20 ` Steve Litt
2018-12-30 10:04 ` Jonathan de Boyne Pollard
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=E1gdJQG-00047Z-01@eggs.gnu.org \
--to=kaction@debian.org \
--cc=916230-quiet@bugs.debian.org \
--cc=gdiazhartusch@gmail.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).