Apache not removing lock directory

[RazorX]

This is for package 2.2.22-1ubuntu1.3 .

The directory "/var/lock/apache2" appears to not be getting removed when apache stops/restarts. If the user/group apache runs under is modified it will fail to start until the folder is manually removed. This appears to be a changed with the latest release and has broken our automation.

Steps to reproduce:
1.) Install apache2 via apt-get.
2.) /etc/init.d/apache2 stop
3.) ls -l /var/lock
You will notice that the apache2 directory has not been removed. The init script will check for its existence and ownership at startup, so if you modify the apache user to anything else it will not start until that directory is removed.

[Robie Basak (racb)]

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

You did not specify any version information in your report. What version of apache2 exhibits this problem? What version did you upgrade from?

And to help developers reproduce your problem, please also specify what the owner/group of /var/lock/apache2 was before, and what it is now.

Once you've answered, please change the bug status back to New. Thanks!

[RazorX (greg-zapp)]

I have updated the bug description with the package version and steps to reproduce. Apache runs as www-data out of the box.

[Robie Basak (racb)]

Thanks - I follow you now.

I've reproduced this behaviour on 2.2.14-5ubuntu8.11 (Lucid), 2.2.22-1ubuntu1.3 (Precise) and 2.2.22-6ubuntu5 (Saucy).

But I can't find any regression as you describe.

The init script does have access to the owner and group configured in /etc/apache2/envvars, so I think it may be a reasonable Wishlist item to have the init script automatically fix up /var/lock/apache2 for you. This is something that is best submitted as a Debian bug, and then if fixed there we can adopt the fix in Ubuntu on the next merge.

If this is a regression, then please provide an example of how to reproduce the problem not occurring in an older release.