389-DS fails to start. Connection to storage server failed error in Roundcube.



  • Hi,

    I installed kolab-16 on a fresh install of Ubuntu 16.04. The installation was successful and I was able to secure the installation using the HOWTO guide in the documentation.
    But after 3 days, I could no longer login to roundcube and it kept throwing this error - "Connection to storage server failed."

    I started to debug and finally found that 389-ds fails to start and this is the output when I try to start the dirsrv-admin:

    Starting dirsrv-admin (via systemctl): dirsrv-admin.serviceJob for dirsrv-admin.service failed because the control process exited with error code. See "systemctl status dirsrv-admin.service" and "journalctl -xe" for details.
    failed!

    This is the output of "systemctl status dirsrv-admin.service":

    dirsrv-admin.service - 389 Administration Server.
    Loaded: loaded (/lib/systemd/system/dirsrv-admin.service; disabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Wed 2017-09-13 06:52:58 UTC; 1min 40s ago
    Process: 6095 ExecStart=/usr/sbin/apache2 -k start -f /etc/dirsrv/admin-serv/httpd.conf (code=exited, status=1/FAILURE)

    This is the output of "journalctl -xe":

    Sep 13 06:52:38 example.org imaps[5806]: inittls: Loading hard-coded DH parameters
    Sep 13 06:52:38 example.org imaps[5806]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits reused) no authentication
    Sep 13 06:52:57 example.org systemd[1]: Starting 389 Administration Server....
    -- Subject: Unit dirsrv-admin.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dirsrv-admin.service has begun starting up.
    Sep 13 06:52:58 example.org systemd[1]: dirsrv-admin.service: Control process exited, code=exited status=1
    Sep 13 06:52:58 example.org systemd[1]: Failed to start 389 Administration Server..
    -- Subject: Unit dirsrv-admin.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dirsrv-admin.service has failed.
    -- The result is failed.
    Sep 13 06:52:58 example.org systemd[1]: dirsrv-admin.service: Unit entered failed state.
    Sep 13 06:52:58 example.org systemd[1]: dirsrv-admin.service: Failed with result 'exit-code'.

    And this is the only error logged in "/var/log/dirsrv/admin-serv/error":

    [Wed Sep 13 06:52:58.000488 2017] [:warn] [pid 6095:tid 140636988450688] NSSSessionCacheTimeout is deprecated. Ignoring.
    [Wed Sep 13 06:52:58.000570 2017] [:crit] [pid 6095:tid 140636988450688] do_admserv_post_config(): unable to create AdmldapInfo
    AH00016: Configuration Failed

    It would be highly helpful if somebody could help me fix this problem.

    Thanks,
    theAngryCoder



  • I don't know if the services are called differently in Ubuntu.
    In CentOS, the service you want is called dirsrv.target.

    systemctl restart dirsrv.target
    systemctl status dirsrv.target