Description of problem: I want use apache mod_auth_form module. To make what I want, I modify the /etc/httpd/conf/modules.d/00_base.conf file and add these lines : LoadModule auth_form_module modules/mod_auth_form.so LoadModule request_module modules/mod_request.so LoadModule session_module modules/mod_session.so LoadModule session_cookie_module modules/mod_session_cookie.so LoadModule session_crypto_module modules/mod_session_crypto.so But when I restard apache, it refuse to start without explicit message : # systemctl restart httpd.service Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details. # 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 jeu. 2013-12-26 11:16:17 CET; 56s ago Process: 5884 ExecStop=/usr/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS) Process: 5882 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE) Main PID: 5882 (code=exited, status=1/FAILURE) Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec" déc. 26 11:16:16 cauldron.planetes systemd[1]: Starting The Apache HTTP Server... déc. 26 11:16:17 cauldron.planetes systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE déc. 26 11:16:17 cauldron.planetes systemd[1]: Failed to start The Apache HTTP Server. déc. 26 11:16:17 cauldron.planetes systemd[1]: Unit httpd.service entered failed state. # journalctl -xn -- Logs begin at lun. 2013-04-08 20:31:28 CEST, end at jeu. 2013-12-26 11:17:19 CET. -- déc. 26 11:15:18 cauldron.planetes dbus[806]: [system] Activation via systemd déc. 26 11:16:15 cauldron.planetes systemd[1]: Stopping The Apache HTTP Server... -- Subject: Unit httpd.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit httpd.service has begun shutting down. déc. 26 11:16:16 cauldron.planetes systemd[1]: Starting The Apache HTTP Server... -- Subject: Unit httpd.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit httpd.service has begun starting up. déc. 26 11:16:17 cauldron.planetes systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE déc. 26 11:16:17 cauldron.planetes systemd[1]: Failed to start The Apache HTTP Server. -- Subject: Unit httpd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit httpd.service has failed. -- -- The result is failed. déc. 26 11:16:17 cauldron.planetes systemd[1]: Unit httpd.service entered failed state. If I only comment the last line in /etc/httpd/conf/modules.d/00_base.conf, apache start successfully. So the session_crypto_module module ship by Mageia have a problem. The problem occurs in Mageia 3 and Cauldron. Version-Release number of selected component (if applicable): apache-2.4.4-7.4.mga3.src.rpm apache-2.4.7-2.mga4.src.rpm Reproducible: Steps to Reproduce:
CC: (none) => guillomovitch, oe
You need to install apr-util-openssl for the session_crypto_module. I'm looking for the best place to add a dependency in the apache package.
Status: NEW => ASSIGNEDAssignee: bugsquad => guillomovitch
CC: guillomovitch => (none)Assignee: guillomovitch => bugsquad
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD