Purpose unclear of unknown file /etc/apache2/apache2.conf.in
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | apache2 (Ubuntu) |
Medium
|
Bryce Harrington | ||
| | Xenial |
Undecided
|
Unassigned | ||
Bug Description
[Impact]
Due to a recent SRU fix, a stray config file template gets installed on Xenial systems when apache2 is installed. This causes no harm in practice but may cause some confusion.
[Test Case]
* Install apache2
* Look for /etc/apache2/
[Where Problems Could Occur]
The fix changes what gets installed to /etc/apache2, so issues to watch for would relate to unexpected changes in the contents of this directory tree.
[Original
I just upgraded apache2:amd64 2.4.18-2ubuntu3.15 --> 2.4.18-2ubuntu3.17 and now there is a file
/etc/
with the following difference to apache2.conf:
% diff -u /etc/apache2/
--- /etc/apache2/
+++ /etc/apache2/
@@ -71,7 +71,7 @@
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
-#Mutex file:${
+___MUTEX___Mutex file:${
#
# PidFile: The file in which the server should record its process
apache2.conf.in is part of the .deb file, see
https:/
apache2.conf.in is not mentioned in any config file in /etc/apache2,
not in the init.d script or systemd service file nor in the changelog.
What's the purpose of that file?
From the diff above it doesn't even look like a valid apache2 config file
because of the "___MUTEX___" prefix.
Is this some kind of leftover from a search/replace operation?
Related branches
- Christian Ehrhardt : Needs Information on 2020-11-17
-
Diff: 30 lines (+12/-1)2 files modifieddebian/apache2.install (+4/-1)
debian/changelog (+8/-0)
| Sergio Durigan Junior (sergiodj) wrote : | #1 |
| Changed in apache2 (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Bryce Harrington (bryce) wrote : | #2 |
Yeah I remember this, thanks for raising it I'll take a look when I get a chance.
| tags: | added: server-next |
| Changed in apache2 (Ubuntu): | |
| assignee: | nobody → Bryce Harrington (bryce) |
| Changed in apache2 (Ubuntu): | |
| status: | Triaged → In Progress |
| Bryce Harrington (bryce) wrote : | #3 |
debian/
debian/
debian/config-dir/* /etc/apache2
debian/a2enmod /usr/sbin
...
We need to backport the changes for apache2.install list config-dir contents more explicitly:
debian/
debian/
debian/
debian/
This covers all the items in Xenial's config-dir that we want, i.e.:
$ ls config-dir/
apache2.conf.in conf-available/ envvars magic mods-available/ ports.conf sites-available/
| description: | updated |
| Changed in apache2 (Ubuntu): | |
| status: | In Progress → Fix Committed |
Hello thermoman, or anyone else affected,
Accepted apache2 into xenial-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
| Changed in apache2 (Ubuntu Xenial): | |
| status: | New → Fix Committed |
| tags: | added: verification-needed verification-needed-xenial |
| Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (apache2/2.4.18-2ubuntu3.18) | #5 |
All autopkgtests for the newly accepted apache2 (2.4.18-
The following regressions have been reported in tests triggered by the package:
passenger/5.0.27-2 (amd64, armhf, s390x, arm64, ppc64el, i386)
mod-wsgi/
apache2/
horizon/
libapache2-
subversion/
php7.0/
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
| Ubuntu SRU Bot (ubuntu-sru-bot) wrote : | #6 |
All autopkgtests for the newly accepted apache2 (2.4.18-
The following regressions have been reported in tests triggered by the package:
libapache2-
php7.0/
mod-wsgi/
subversion/
horizon/
apache2/
passenger/5.0.27-2 (amd64, armhf, arm64, i386, ppc64el, s390x)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
| Ubuntu SRU Bot (ubuntu-sru-bot) wrote : | #7 |
All autopkgtests for the newly accepted apache2 (2.4.18-
The following regressions have been reported in tests triggered by the package:
mod-wsgi/
php7.0/
passenger/5.0.27-2 (arm64, s390x, amd64, i386, armhf, ppc64el)
apache2/
subversion/
horizon/
libapache2-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
Thanks for your report and for making Ubuntu better.
I can confirm this bug. The .in file was added as of:
apache2 (2.4.18-
* On Linux, use pthread mutexes. On kfreebsd/hurd, continue using
fctnl because they lack robust pthread mutexes.
(LP: #1565744)
-- Bryce Harrington <email address hidden> Thu, 16 Jul 2020 00:20:55 +0000
but you're correct in saying that the changelog entry does not mention the file. You are also correct in your guess: the file is a leftover of a search-and-replace operation; it should have probably been removed after the replace took place.
Even though the .in file is harmless (Apache will not try to load it in any way), it should not have been installed. I am marking this bug as Triaged and will contact Bryce to sync.
Thanks!