From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2425 Path: news.gmane.org!.POSTED!not-for-mail From: Dmitry Bogatov Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Log rotation issue with runit Date: Sat, 29 Dec 2018 18:33:18 +0000 Message-ID: References: <20181226015822.GH29946@home.lan> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1546108281 6465 195.159.176.226 (29 Dec 2018 18:31:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 29 Dec 2018 18:31:21 +0000 (UTC) Cc: Supervision , 916230-quiet@bugs.debian.org To: Guillermo Original-X-From: supervision-return-2015-gcsg-supervision=m.gmane.org@list.skarnet.org Sat Dec 29 19:31:16 2018 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1gdJOG-0001Vw-7r for gcsg-supervision@m.gmane.org; Sat, 29 Dec 2018 19:31:16 +0100 Original-Received: (qmail 32286 invoked by uid 89); 29 Dec 2018 18:33:52 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 32279 invoked from network); 29 Dec 2018 18:33:52 -0000 In-reply-to: Comments: In-reply-to Guillermo message dated "Thu, 27 Dec 2018 20:39:17 -0300." Content-ID: <21226.1546108398.1@neophite> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2425 Archived-At: [2018-12-27 20:39] Guillermo > El jue., 27 dic. 2018 a las 6:36, Dmitry Bogatov escribi=C3=B3: > > > > 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'?