[Pkg-fedora-ds-maintainers] 389-admin

Attila Bárdi attila.bardi at gmail.com
Thu Dec 12 14:35:55 UTC 2013


I installed the 389-ds to my test system:

root at station18:~# dpkg -l 389*
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                               Version                Architecture
ii  389-admin                          1.1.30-1+b1            i386
          389 Directory Administration Server
ii  389-admin-console                  1.1.8-1                all
         389 admin server management console
ii  389-console                        1.1.7-1                all
         389 Management Console
ii  389-ds                                 all
         389 Directory Server suite - metapackage
ii  389-ds-base                         i386
          389 Directory Server suite - server
ii  389-ds-base-libs                    i386
          389 Directory Server suite - libraries
ii  389-ds-console                     1.2.6-1                all
         389 Directory Server Management Console
ii  389-ds-console-doc                 1.2.6-1                all
         389 Directory Server Management Console -- documentation
ii  389-dsgw                           1.1.9-1+b1             i386
          389 Directory Server Gateway
root at station18:~#

My debian is a stable release with possibilities to install packages from
testing and unstable:

root at station18:~# cat /etc/apt/preferences
Package: *
Pin: release a=stable
Pin-Priority: 900

Package: *
Pin: release a=testing
Pin-Priority: 400

Package: *
Pin: release a=unstable
Pin-Priority: 300
root at station18:~#

When I tried to install the 389-admin the apache failed to start:

Are you ready to set up your servers? [yes]:
Creating directory server . . .
Your new DS instance 'station18' 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: AH00534: apache2: Configuration error: No MPM loaded.
output: Server failed to start !!! Please check errors log for problems
Could not start the admin server.  Error: 256
Failed to create and configure the admin server
Exiting . . .
Log file is '/tmp/setupCSSxQy.log'

After some checking it turned out there are missing modules from

LoadModule mpm_event_module /usr/lib/apache2/modules/mod_mpm_event.so
LoadModule authn_core_module /usr/lib/apache2/modules/mod_authn_core.so
LoadModule access_compat_module
LoadModule authz_core_module /usr/lib/apache2/modules/mod_authz_core.so
LoadModule authz_user_module /usr/lib/apache2/modules/mod_authz_user.so

With those lines in the config the 389-admin (apache) successfully started.

Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-fedora-ds-maintainers/attachments/20131212/60df00ae/attachment.html>

More information about the Pkg-fedora-ds-maintainers mailing list