cronolog.org
flexible web log rotation
HOME
DOWNLOAD
FEATURES
USAGE
FAQ
BLOG
KNOWN BUGS
SECURITY
PATCHES
USERS
TO DO
HISTORY
LINKS
FEEDBACK
MAILING LIST
ADVERTISING

support cronolog development



Google   HELP


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CRONOLOG: RE: piped program error



Ryan,

do you get the error at midnight of whatever time zone you're using?
do you reliably get it every time?  exactly once or a bunch of times?

you might want to double check that the user who is running apache has
the necessary permissions to do everything it is supposed to.

one way of debugging cronolog without running apache is to do something
like :

while :; do date ; sleep 1 ; done | /sbin/cronolog <your options>

with a one minute rotation time. That might help you find the error.

regards,
Matt

On Oct 24 1118, Ryan C. Creasey wrote:
> Hello,
> 
> I've been a long user of cronolog and have found it to be extremely
> helpful in organizing my apache logs.  Well, just recently I've started
> to have odd problems...  I'm getting the following error in my apache
> error logs:
> 
> piped log program '/sbin/cronolog
> --symlink=/var/log/httpd/belial.p11.com/current.log
> /var/log/httpd/belial.p11.com/%m%y/access.%d.log' failed unexpectedly
> 
> I'm using cronolog-1.6.2 with apache-2.0.47 and am invoking it like so:
> CustomLog "|/sbin/cronolog -S /var/log/httpd/belial.p11.com/current.log
> var/log/httpd/belial.p11.com/%m%y/access.%d.log" "%h %l %u %t \"%r\" %s
> %b \"%{Referer}i\" \"%{User-agent}i\""
> 
> I've got it organized like so:
> root@xxxxxxxxxxxxxx:/home/misc/httpd/conf# ls -la /var/log/httpd 
> lrwxr-xr-x  1 root  wheel  28 Oct 23 08:51 /var/log/httpd ->
> /projects/sites/logs.p11.com
> root@xxxxxxxxxxxxxx:/home/misc/httpd/conf# ls -la
> /projects/sites/logs.p11.com/error/
> total 6
> drwxrwxr-x   3 root  wheel   512 Oct 23 09:20 .
> drwxrwxr-x  18 root  wheel   512 Oct 13 13:59 ..
> drwxr-xr-x   2 root  wheel   512 Oct 23 09:20 1003
> lrwxr-xr-x   1 root  office   38 Oct 23 09:20 current.log ->
> /var/log/httpd/error/1003/error.23.log
> 
> So what could be causing this error in my apache logs?  I've tried
> setting the debug options, but that doesn't seem to display any relavant
> information.  I've been using it this way for a long time and never
> remember it having any problems.  This isn't something I can ignore, as
> I'm getting one of these logs for every access log that is being
> entered.
> 
> Any thoughts?
> 
> --
> Ryan C. Creasey
> Network Engineer
> p11creative, inc.
> 

-- 
#######################################################################
# Matt Grosso           cell    (201)780-9592   mgrosso@xxxxxxxxxxxxx #
# work ny (212)324-1904 fax ny  (212)324-1910   work sf (415)348-7756 #
# pgp public key is at http://www.falconweb.com/~mattg/publickey.pgp  #
#######################################################################




Copyright © 1996-2004 Andrew Ford and Ford & Mason Ltd