<div dir="ltr">Hey,<div><br></div><div>I installed the 389-ds to my test system:</div><div><br></div><font face="courier new, monospace">root@station18:~# dpkg -l 389*<br>Desired=Unknown/Install/Remove/Purge/Hold<br>| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend<br>
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)<br>||/ Name Version Architecture Description<br>+++-==================================-======================-======================-=========================================================================<br>
ii 389-admin 1.1.30-1+b1 i386 389 Directory Administration Server<br>ii 389-admin-console 1.1.8-1 all 389 admin server management console<br>
ii 389-console 1.1.7-1 all 389 Management Console<br>ii 389-ds 1.3.0.3-1 all 389 Directory Server suite - metapackage<br>
ii 389-ds-base 1.3.0.3-1+b2 i386 389 Directory Server suite - server<br>ii 389-ds-base-libs 1.3.0.3-1+b2 i386 389 Directory Server suite - libraries<br>
ii 389-ds-console 1.2.6-1 all 389 Directory Server Management Console<br>ii 389-ds-console-doc 1.2.6-1 all 389 Directory Server Management Console -- documentation<br>
ii 389-dsgw 1.1.9-1+b1 i386 389 Directory Server Gateway<br>root@station18:~#</font><div><br><div>My debian is a stable release with possibilities to install packages from testing and unstable:</div>
<div><br></div><div><div>root@station18:~# cat /etc/apt/preferences</div><div>Package: *</div><div>Pin: release a=stable</div><div>Pin-Priority: 900</div><div><br></div><div>Package: *</div><div>Pin: release a=testing</div>
<div>Pin-Priority: 400</div><div><br></div><div>Package: *</div><div>Pin: release a=unstable</div><div>Pin-Priority: 300</div><div>root@station18:~# </div></div><div><br></div><div><br></div><div>When I tried to install the 389-admin the apache failed to start:</div>
<div><br></div><div><div>Are you ready to set up your servers? [yes]: </div><div>Creating directory server . . .</div><div>Your new DS instance 'station18' was successfully created.</div><div>Creating the configuration directory server . . .</div>
<div>Beginning Admin Server creation . . .</div><div>Creating Admin Server files and directories . . .</div><div>Updating adm.conf . . .</div><div>Updating admpw . . .</div><div>Registering admin server with the configuration directory server . . .</div>
<div>Updating adm.conf with information from configuration directory server . . .</div><div>Updating the configuration for the httpd engine . . .</div><div>Starting admin server . . .</div><div>output: AH00534: apache2: Configuration error: No MPM loaded.</div>
<div>output: Server failed to start !!! Please check errors log for problems</div><div>Could not start the admin server. Error: 256</div><div>Failed to create and configure the admin server</div><div>Exiting . . .</div><div>
Log file is '/tmp/setupCSSxQy.log'</div><div><br></div></div><div><br></div><div>After some checking it turned out there are missing modules from /etc/dirsrv/admin-serv/httpd.conf:</div><div><br></div><div><div><font face="courier new, monospace">LoadModule mpm_event_module /usr/lib/apache2/modules/mod_mpm_event.so</font></div>
<div><font face="courier new, monospace">LoadModule authn_core_module /usr/lib/apache2/modules/mod_authn_core.so</font></div><div><font face="courier new, monospace">LoadModule access_compat_module /usr/lib/apache2/modules/mod_access_compat.so</font></div>
<div><font face="courier new, monospace">LoadModule authz_core_module /usr/lib/apache2/modules/mod_authz_core.so</font></div><div><font face="courier new, monospace">LoadModule authz_user_module /usr/lib/apache2/modules/mod_authz_user.so</font></div>
</div><div><br></div><div><br></div><div>With those lines in the config the 389-admin (apache) successfully started.</div><div><br></div><div>Best regards,</div><div>Attila</div></div></div>