Re: apache2 logs -> svlogd

["George Georgalis" <george@galis.org>]

On Mon, Feb 13, 2006 at 08:25:20PM +0200, Alex Efros wrote:
>
>    ----- Forwarded message from Joshua N Pritikin <jpritikin@pobox.com> -----
>    Date: Wed, 7 Dec 2005 17:35:42 +0530
>    From: Joshua N Pritikin <jpritikin@pobox.com>
>    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 <prj <at> po.cwru.edu>
Subject: Re: svlogd choaking on lock
Newsgroups: gmane.comp.sysutils.supervision.general

Joshua N Pritikin <jpritikin <at> 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 <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org