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

[Timo Aaltonen]

On 12.12.2013 16:35, Attila Bárdi wrote:
> Hey,
> 
> I installed the 389-ds to my test system:
> 
> root at station18:~# dpkg -l 389*
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name                               Version              
>  Architecture           Description
> +++-==================================-======================-======================-=========================================================================
> 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                             1.3.0.3-1              all      
>              389 Directory Server suite - metapackage
> ii  389-ds-base                        1.3.0.3-1+b2           i386      
>             389 Directory Server suite - server
> ii  389-ds-base-libs                   1.3.0.3-1+b2           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
> /etc/dirsrv/admin-serv/httpd.conf:
> 
> 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
> /usr/lib/apache2/modules/mod_access_compat.so
> 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.

Thanks, could be due to apache migrating to 2.4. I'll fix it soon.


-- 
t