/etc/logrotate.d/apache2 ignores changes to $APACHE_LOG_DIR

Bug #1298739 reported by Serhiy
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)

Bug Description

I've edited $APACHE_LOG_DIR in the envvars file and in order to make logrotate work I have to edit /etc/logrotate.d/apache2 also.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apache2 2.4.7-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
Apache2ConfdDirListing: False
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Mar 28 04:16:19 2014
SourcePackage: apache2
UpgradeStatus: No upgrade log present (probably fresh install)
error.log: Error: [Errno 2] No such file or directory: '/var/log/apache2/error.log'
modified.conffile..etc.apache2.envvars: [modified]
mtime.conffile..etc.apache2.envvars: 2014-03-28T03:54:01.458056

Revision history for this message
Serhiy (xintx-ua) wrote :
Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

It would certainly be nice for logrotate to automatically pick up changes to /etc/apache2/envvars in case of local changes, but I'm not sure it's possible to configure logrotate to examine /etc/apache2/envvars at all. I don't see any mechanism in the logrotate configuration file format to do this.

I think it would be reasonable to say that a sysadmin who wants to change the log directory must change all appropriate locations, including /etc/logrotate.d/apache2, as part of the interface currently provided by packaging.

So while it would be nice for this to be automatic somehow, I think this a wishlist item as that is not the current interface. It's additionally complex to arrange without an existing mechanism for logrotate to dynamically peek into other packages' configuration files as part of its own configuration.

Changed in apache2 (Ubuntu):
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.