httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Reilly <>
Subject Re: [users@httpd] access.log problem
Date Wed, 12 Dec 2007 23:00:12 GMT

> Try the following:
> root> su - apache
> apache> cd /var/log/apache
> apache> echo test > access.log

well, I think I might be making some progress, the above did in fact
write test to the access.log (i physically made this log, not apache)
> That of course assumes that 'apache' is a working user, with a login
> shell, but you get the idea.
> Furthermore check what your logrotate does. Are the access.log.*
> files written by Apache itself (using a log statement configuration
> that pipes into a log rotator) or via a cron driven logrotate? In
> the latter case, Apache doesn't need to write access.log.1 and "tail
> -f" on the file wouldn't be too useful.

I did not touch the base config for debian etch when I installed the
server last year.   Im also not too familiar with logrotate, Im going to
assume it is the standard debian install as I have touched nothing. 
Last I knew before the contents of /var/log/apache2 was deleted there
was access.log, access.log.1 text files and then tars of .2 through
.28.  I made the access.log and access.log.1 to see if apache would
write anything to it. no dice yet.

> What are the exact permissions of: /var, /var/log,
/var owned by root, and root filegroup 1600755
/var/log owned by root, and  root filegroup 1600755
/var/log/apache2 owned by root, and root filegroup 1600755
/var/log/apache2/access.log owned by root, root filegroup 1600644
/var/log/apache2/error.log owned by root, root filegroup 600644

I made the access.log the same permissions as error.log, was that wrong?

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message