VLOG issues after upgrade 1.3.33-r5 to 1.3.34-r10 [SOLVED]

[geowapa]

I finally upgraded my production server from 1.3.33-r4 to 1.3.34-r10. No issues with the configuration files, however I've discovered that it was no longer logging. My test server seemed to upgrade fine, but there was so little activity, I didn't notice that the logs were missing.

In looking at the configuration upgrade, all mention of apachesplitlogfile and the VLOG environment variable is deleted. I added the following lines back into httpd.conf, and added the Setenv VLOG to the vhost definitions

CustomLog logs/access_log combined env=!VLOG
# If VLOG is defined in conf/vhosts/Vhosts.conf, we use this entry
CustomLog "|/usr/sbin/apachesplitlogfile" vhost env=VLOG

The apachesplitlogfile process starts and appears active in the system, but nothing gets written to the log files at all. A zero-length "vhost.log" is created. If I comment out the Setenv for a vhost, it starts logging to the access_log file.

It almost appears as if the "vhost" is being passed literally instead of the vhost name, resulting in the zero length vhost.log

Can anyone comment - with the new apache configuration layout, is there any way to use apachesplitlogfile, or is it deprecated? I can't find any meaningful mentions of it in the Bugzilla system or in the forums.

Thanks,
George

[geowapa]

Never mind... Turns out the new Apache definitions are missing the required LogFormat statement.

Adding the following to httpd.conf restores the VLOG logging

LogFormat "%v %h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" VLOG=%{VLOG}e" vhost

George