From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2174 Path: news.gmane.org!not-for-mail From: Vallo Kallaste Newsgroups: gmane.comp.sysutils.supervision.general Subject: s6-log taking 100% CPU Date: Thu, 13 Dec 2012 16:19:25 +0200 Message-ID: <20121213141924.GA16171@hape.internal> Reply-To: kalts@estpak.ee NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1355408368 19501 80.91.229.3 (13 Dec 2012 14:19:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Dec 2012 14:19:28 +0000 (UTC) To: supervision@list.skarnet.org Original-X-From: supervision-return-2408-gcsg-supervision=m.gmane.org@list.skarnet.org Thu Dec 13 15:19:42 2012 Return-path: Envelope-to: gcsg-supervision@plane.gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Tj9dU-00041Q-Lj for gcsg-supervision@plane.gmane.org; Thu, 13 Dec 2012 15:19:40 +0100 Original-Received: (qmail 23852 invoked by uid 76); 13 Dec 2012 13:16:27 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 23844 invoked from network); 13 Dec 2012 13:16:26 -0000 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2174 Archived-At: Hi I have noticed that s6-log enters busyloop after failing to rotate the log. Some data: * I don't have strace output at hand, but from memory it was infinite stream of identical poll() related lines. * s6-log runs as: s6-log -b s16777215 n25 S0 !xz -0q /var/service/nslcd/log * Happens only for service loggers missing the log/state file. Most service loggers do not have the log/state file, this is probably my mistake in some deployment script. * There are following lines in s6-svscan log: s6-log (processor child): fatal: unable to open_readb /var/service/nslcd/log/state: No such file or directory s6-log: warning: processor failed in /var/service/nslcd/log It seems that this is caused by my mistake but perhaps it could be handled better? BR, -- Vallo