Re: Need help to diagnose a problem with CustomLog

[Igor Cicimov <icicimov@xxxxxxxxx>]

Maybe in some other config file that has been included in the main config file via Include statement? I don't see any reason for apache to log something unless told to.

On Wed, Oct 7, 2009 at 11:28 PM, Bernard Fay <bernard.fay@xxxxxxxxx> wrote:

Thanks Igor for your reply,

Actually, /var/log/apache2/access_log is not commented out, it is not there at all in the config file.
I have only CustomLog in a vhost configuation file which is called by an Include directive.

There is nothing overly complex in my setup.  That's why I am totally puzzled with this.  8-|

By the way, this is Apache/2.2.3 running on SuSE SLES 10 with SP1.

On Tue, Oct 6, 2009 at 7:24 PM, Igor Cicimov <icicimov@xxxxxxxxx> wrote:

Have you commented out the /var/log/apache2/access_log line in the main section of the config file?

On Wed, Oct 7, 2009 at 6:09 AM, Bernard Fay <bernard.fay@xxxxxxxxx> wrote:

Hi,

I have a weird problem with CustomLog. 

I defined an access log in a vhost configuration file.  This site used to use /var/log/apache2/access_log.  I changed it to use "CustomLog /var/log/apache2/www.services.cnt.qc/www.services.cnt.qc-access_log combined"

For some odd reason, when I started Apache it created my desired access log file but keep writing in /var/log/apache2/access_log.  I did stop and start Apache2 but without success.

Does soemone know why?

What can be done to diagnose this problem?

I checked the configuration file many times and everything is ok.

Thanks in advance,
Bernard