Current time: 09-28-2024, 05:42 AM Hello There, Guest! (LoginRegister)


Post Reply 
Replicated apache logs
Author Message
kilburn Offline
Development Team
*****
Dev Team

Posts: 2,182
Joined: Feb 2007
Reputation: 34
Post: #1
Replicated apache logs
I was checking the status of my servers when I've realized that the one currently running ispcp 1.0 had a strange, fat, apache logfile named other_vhosts_access.log.

After looking for it's origin, I've seen that it is defined in debian lenny's default /etc/apache2/apache2.conf:
Code:
...
# Define an access log for VirtualHosts that don't define their own logfile
CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined
...

This wasn't a problem before introducing the new apache log processor because those days ispcp defined a CustomLog for each VirtualHost which effectively wipped out this directive (CustomLogs on VirtualHosts override CustomLogs on the base configuration).

After the new log processing engine tough, ispcp defines a new single log on the base configuration. Moreover, as CustomLogs on base configuration are additive, we end up having both the ispcp controlled logfiles and this "other_vhosts_access.log" file which replicates everything.

IMHO the debian's default CustomLog directive can (and should) be commented safely. Any comments or idea to let ispcp's installation take care of it?
(This post was last modified: 03-25-2009 07:22 PM by kilburn.)
03-25-2009 07:17 PM
Visit this user's website Find all posts by this user Quote this message in a reply
Post Reply 


Messages In This Thread
Replicated apache logs - kilburn - 03-25-2009 07:17 PM
RE: Replicated apache logs - BeNe - 03-25-2009, 07:35 PM
RE: Replicated apache logs - kilburn - 03-25-2009, 07:44 PM

Forum Jump:


User(s) browsing this thread: 3 Guest(s)