Bug 10504 - Apache update does not set the new httpd.conf
Summary: Apache update does not set the new httpd.conf
Status: RESOLVED DUPLICATE of bug 6805
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-06-12 08:32 CEST by Franz Holzinger
Modified: 2013-06-13 11:16 CEST (History)
0 users

See Also:
Source RPM: apache
CVE:
Status comment:


Attachments

Description Franz Holzinger 2013-06-12 08:32:06 CEST
Description of problem:
Apache cannot start because it fails to load the mod_authn_default.so.
I did an online upgrade from a working Mageia2 to Mageia3. Now Apache refuses to start.

Version-Release number of selected component (if applicable):
apache-2.4.4-7.mga3

/etc/httpd/conf/httpd.conf :
LoadModule authn_default_module modules/mod_authn_default.so


--------------------------------
[root@localhost etc]# rpm -qf `which apache`
which: no apache in (/usr/local/sbin:/usr/sbin:/usr/local/bin:/usr/bin)
rpm: aucun argument fournit à la requête
[root@localhost etc]# systemctl status httpd.service
httpd.service - The Apache HTTP Server
          Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
          Active: failed (Result: exit-code) since Wed, 2013-06-12 08:19:33 CEST; 10min ago
         Process: 31637 ExecStop=/usr/sbin/httpd $OPTIONS -k graceful-stop (code=exited, status=1/FAILURE)
         Process: 31634 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/httpd.service

Jun 12 08:19:33 localhost.localdomain systemd[1]: Starting The Apache HTTP Server...
Jun 12 08:19:33 localhost.localdomain httpd[31634]: httpd: Syntax error on line 227 of /etc/httpd/conf/httpd.conf: Cannot load modules/mod_authn_default.so into server... directory
Jun 12 08:19:33 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jun 12 08:19:33 localhost.localdomain httpd[31637]: httpd: Syntax error on line 227 of /etc/httpd/conf/httpd.conf: Cannot load modules/mod_authn_default.so into server... directory
Jun 12 08:19:33 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
Jun 12 08:19:33 localhost.localdomain systemd[1]: Unit httpd.service entered failed state



Reproducible: 

Steps to Reproduce:
Comment 1 Franz Holzinger 2013-06-12 15:43:23 CEST
You must do the following:

# cd  /etc/httpd/conf
# cp  httpd.conf  httpd.conf.old
# cp  httpd.conf.rpmnew  httpd.conf
cp : voulez-vous écraser « httpd.conf » ? y


Then apache will work.
Unfortunately the upgrade installation does not do this by itself and it does not even tell the user what he has to do.
Franz Holzinger 2013-06-12 15:44:40 CEST

Summary: Apache fails to load mod_authn_default.so => Apache update does not set the new httpd.conf

Manuel Hiebel 2013-06-12 23:05:01 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => guillomovitch
Source RPM: (none) => apache

Comment 2 Guillaume Rousse 2013-06-13 00:05:09 CEST
Problem already discussed before release, without proper automated solution. But this is clearly documented in README.urpmi.

*** This bug has been marked as a duplicate of bug 6805 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE

Comment 3 Franz Holzinger 2013-06-13 06:42:00 CEST
Where is the file README.urpmi?

There is no such file under /etc/httpd/conf .
Comment 4 Guillaume Rousse 2013-06-13 09:09:22 CEST
As for every other README file, for every package: under /usr/share/doc/<package>
Comment 5 Franz Holzinger 2013-06-13 09:52:30 CEST
Thanks, I have found it now.
Why isn't this information shown in any error message after the upgrade to Mageia3?
Comment 6 Guillaume Rousse 2013-06-13 11:16:21 CEST
If you upgrade through urpmi, this is displayed on the console.
If you upgrade through rpmdrake, this is displayed in a popup.
If you upgrade through the installer or through the applet, I don't think this is displayed anywhere. This could be added to the release notes, tough.

Note You need to log in before you can comment on or make changes to this bug.