From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1022 Path: news.gmane.org!not-for-mail From: Alex Efros Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: apache2 logs -> svlogd Date: Mon, 13 Feb 2006 20:25:20 +0200 Organization: asdfGroup Inc., http://powerman.asdfGroup.com/ Message-ID: <20060213182520.GE6585@home.power> References: <20060213173813.GA6585@home.power> <20060213180402.GA30800@wolfpuppy.org.uk> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1139855145 27322 80.91.229.2 (13 Feb 2006 18:25:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 13 Feb 2006 18:25:45 +0000 (UTC) Original-X-From: supervision-return-1258-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Feb 13 19:25:41 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 1F8iO1-0005bZ-R0 for gcsg-supervision@gmane.org; Mon, 13 Feb 2006 19:25:22 +0100 Original-Received: (qmail 5467 invoked by uid 76); 13 Feb 2006 18:25:43 -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 5461 invoked from network); 13 Feb 2006 18:25:42 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20060213180402.GA30800@wolfpuppy.org.uk> User-Agent: Mutt/1.5.11 Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1022 Archived-At: Hi! On Mon, Feb 13, 2006 at 06:04:02PM +0000, Torne Wuff wrote: > Apache can do this without any external help from FIFOs etc, just use a > configuration like this: I know about this. But AFAIK there some problems with this way, for ex.: ----- 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. -- WBR, Alex.