From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1042 Path: news.gmane.org!not-for-mail From: "George Georgalis" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: apache2 logs -> svlogd Date: Tue, 14 Feb 2006 09:25:32 -0500 Message-ID: <20060214142532.GA1378@sta.duo> References: <20060213173813.GA6585@home.power> <20060213180402.GA30800@wolfpuppy.org.uk> <20060213182520.GE6585@home.power> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1139927141 12815 80.91.229.2 (14 Feb 2006 14:25:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Feb 2006 14:25:41 +0000 (UTC) Original-X-From: supervision-return-1278-gcsg-supervision=m.gmane.org@list.skarnet.org Tue Feb 14 15:25:34 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1F917W-0002f5-2p for gcsg-supervision@gmane.org; Tue, 14 Feb 2006 15:25:34 +0100 Original-Received: (qmail 18791 invoked by uid 76); 14 Feb 2006 14:25:55 -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 18786 invoked from network); 14 Feb 2006 14:25:55 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20060213182520.GE6585@home.power> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1042 Archived-At: On Mon, Feb 13, 2006 at 08:25:20PM +0200, Alex Efros wrote: > > ----- Forwarded message from Joshua N Pritikin ----- > Date: Wed, 7 Dec 2005 17:35:42 +0530 > From: Joshua N Pritikin > To: supervision@list.skarnet.org > Subject: svlogd choaking on lock > > Hi! > > I'm using svlogd for apache2 access logs. However, this is not working > too well. The problem is that when apache restarts, say a graceful USR1 > restart, then it kills the old svlogd and starts a new one fast enough > that I almost always get: > > svlogd: warning: unable to lock directory: /var/log/apache2/access: > temporary failure > svlogd: fatal: no functional log directories. > > The error log was exhibiting the same problem but then I figured out how > to route the ErrorLog through /dev/fd/3 and then runsv took care of not > restarting svlogd. So only the access log problem remains. > > Suggestions? > > -- > Make April 15 just another day, visit http://fairtax.org > > ----- End forwarded message ----- > >Recommended solution was put 'sleep 1' before svlogd, but for me it's a >little ugly and unreliable. I just checked that thread on gmane. ---------------------------------------- Date: 2005-12-07 16:04:02 GMT From: Paul Jarc po.cwru.edu> Subject: Re: svlogd choaking on lock Newsgroups: gmane.comp.sysutils.supervision.general Joshua N Pritikin pobox.com> wrote: > The problem is that when apache restarts, say a graceful USR1 > restart, then it kills the old svlogd and starts a new one fast enough > that I almost always get: > > svlogd: warning: unable to lock directory: /var/log/apache2/access: temporary failure > svlogd: fatal: no functional log directories. You could change your svlogd invocation to "sleep 1 && svlogd ...". paul ---------------------------------------- Since I only use svlogd for ErrorLog and one process for each virtual domain, I'm interested in making this approach work. But I don't completely understand what the problem is; or the downside of using "sleep 1 && svlogd ..." -- I understand it would use ulimit resources (filling the pipe) till svlogd starts, but so what? Something ugly _might_ be apache pipe exec... something more reliable might be a loop to restart svlogd if it fails. Thoughts? // George -- George Georgalis, systems architect, administrator < http://galis.org/ cell:646-331-2027 mailto:george@galis.org