From: Joshua N Pritikin <jpritikin@pobox.com>
Subject: svlogd choaking on lock
Date: Wed, 7 Dec 2005 17:35:42 +0530 [thread overview]
Message-ID: <20051207120542.GF10371@always.joy.eth.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-12-07 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 12:05 Joshua N Pritikin [this message]
2005-12-07 16:04 ` Paul Jarc
2005-12-07 16:43 ` Joshua N Pritikin
2005-12-07 17:24 ` Bernhard Graf
2005-12-07 17:38 ` Joshua N Pritikin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051207120542.GF10371@always.joy.eth.net \
--to=jpritikin@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).