Reported by the CS team: My directory server admin server installation failed on my new F18 VM, dogtag18.example.com:
Creating directory server . . . Your new DS instance 'dogtag18' was successfully created. Creating the configuration directory server . . . Beginning Admin Server creation . . . Creating Admin Server files and directories . . . Updating adm.conf . . . Updating admpw . . . Registering admin server with the configuration directory server . . . Updating adm.conf with information from configuration directory server . . . Updating the configuration for the httpd engine . . . Starting admin server . . . output: Job for dirsrv-admin.service failed. See 'systemctl status dirsrv-admin.service' and 'journalctl -n' for details. Could not start the admin server. Error: 256 Failed to create and configure the admin server Exiting . . . Log file is '/tmp/setupmJenSb.log' # journalctl -n -- Logs begin at Wed, 2012-10-31 11:58:58 PDT, end at Wed, 2012-10-31 14:26:02 P Oct 31 14:20:38 dogtag18.example.com systemd[1]: Unit dirsrv-admin.servic Oct 31 14:20:49 dogtag18.example.com dbus-daemon[466]: dbus[466]: [system Oct 31 14:20:49 dogtag18.example.com dbus[466]: [system] Reloaded configu Oct 31 14:21:00 dogtag18.example.com dbus-daemon[466]: dbus[466]: [system Oct 31 14:21:00 dogtag18.example.com dbus[466]: [system] Reloaded configu Oct 31 14:21:00 dogtag18.example.com su[6075]: pam_unix(su-l:session): se Oct 31 14:22:02 dogtag18.example.com /USR/SBIN/CROND[6202]: (root) CMD (/ Oct 31 14:22:20 dogtag18.example.com avahi-daemon[464]: Received response Oct 31 14:24:02 dogtag18.example.com /USR/SBIN/CROND[6226]: (root) CMD (/ Oct 31 14:26:02 dogtag18.example.com /USR/SBIN/CROND[6252]: (root) CMD (/ # systemctl status dirsrv-admin.service dirsrv-admin.service - 389 Administration Server. Loaded: loaded (/usr/lib/systemd/system/dirsrv-admin.service; enabled) Active: failed (Result: exit-code) since Wed, 2012-10-31 14:20:38 PDT; 7min ago Process: 6073 ExecStart=/usr/sbin/httpd -k start -f /etc/dirsrv/admin-serv/httpd.conf (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/dirsrv-admin.service Oct 31 14:20:38 dogtag18.example.com httpd[6073]: AH00534: httpd: Conf... Oct 31 14:20:38 dogtag18.example.com systemd[1]: Failed to start 389 A... Oct 31 14:20:38 dogtag18.example.com systemd[1]: Unit dirsrv-admin.ser...
It looks the admin server is complaining that the httpd MPM module is missing...
These are snippets of the /var/log/messages on your F18 host dogtag18.example.com:
Oct 31 10:49:26 dogtag18 httpd[514]: AH00534: httpd: Configuration error: No MPM loaded. Oct 31 10:49:26 dogtag18 systemd[1]: Started Sendmail Mail Transport Agent. Oct 31 10:49:26 dogtag18 systemd[1]: Starting Sendmail Mail Transport Client... Oct 31 10:49:26 dogtag18 systemd[1]: dirsrv-admin.service: control process exited, code=exited status=1 Oct 31 10:49:26 dogtag18 systemd[1]: Failed to start 389 Administration Server.. Oct 31 10:49:26 dogtag18 systemd[1]: Unit dirsrv-admin.service entered failed state Oct 31 18:09:49 dogtag18 systemd[1]: Starting 389 Administration Server.... Oct 31 18:09:50 dogtag18 httpd[10721]: AH00534: httpd: Configuration error: No MPM loaded.
On F18, mpm is provided as modules:
[root@dogtag18 admin-serv]# rpm -ql httpd | egrep mpm /etc/httpd/conf.modules.d/00-mpm.conf /usr/lib64/httpd/modules/mod_mpm_event.so /usr/lib64/httpd/modules/mod_mpm_prefork.so /usr/lib64/httpd/modules/mod_mpm_worker.so /usr/share/doc/httpd-2.4.3/httpd-mpm.conf
It was not before... E.g., on F16,
# rpm -ql httpd | egrep mpm # # rpm -ql httpd | egrep worker /lib/systemd/system/httpd-worker.service /usr/sbin/httpd.worker /usr/share/man/man8/httpd.worker.8.gz
Most likely, we have to adjust admin server's config file to the new apache...
Duplicate of Ticket 476 https://fedorahosted.org/389/ticket/476
Metadata Update from @nhosoi: - Issue assigned to rmeggins - Issue set to the milestone: 389-admin,console 1.1.31
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/501
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Duplicate)
Login to comment on this ticket.