SLAPD can not start

My YunoHost server

**Hardware: Hosted Virtual Server with Debian 10
**YunoHost version: 4.1.6
**I have access to my server : Through SSH
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

Hello :slight_smile:

My name is Frank I’m new to Linux and Yunohost and very surprised to get a mail about problems with SLAPD.

After checking the server i found that i could not restart the slapd service.

I found some tips that the service is not terminated correct but it’s not clear to me how i can fix this in the yunohost enviroment.

Here is the log:

        journalctl
        -- Logs begin at Mon 2021-01-25 02:34:41 CET, end at Thu 2021-02-04 21:08:08 CET. --
Feb 04 21:07:58 systemd[1]: Stopped LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Feb 04 21:07:58 systemd[1]: slapd.service: Found left-over process 13994 (slapd) in control group while starting unit. Ignoring.
Feb 04 21:07:58 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Feb 04 21:07:58 systemd[1]: Starting LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)...
Feb 04 21:07:58 slapd[31420]: @(#) $OpenLDAP: slapd  (Jan 22 2021 03:54:40) $
                                      Debian OpenLDAP Maintainers <pkg-openldap-devel@lists.alioth.debian.org>
Feb 04 21:07:58 slapd[31420]: daemon: bind(8) failed errno=98 (Address already in use)
Feb 04 21:07:58 slapd[31420]: slapd stopped.
Feb 04 21:07:58 slapd[31420]: connections_destroy: nothing to destroy.
Feb 04 21:07:58 slapd[31415]: Starting OpenLDAP: slapd failed!
Feb 04 21:07:58 systemd[1]: slapd.service: Control process exited, code=exited, status=1/FAILURE
Feb 04 21:07:58 systemd[1]: slapd.service: Failed with result 'exit-code'.
Feb 04 21:07:58 systemd[1]: Failed to start LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Feb 04 21:08:01 systemd[1]: slapd.service: Service RestartSec=3s expired, scheduling restart.
Feb 04 21:08:01 systemd[1]: slapd.service: Scheduled restart job, restart counter is at 285.
Feb 04 21:08:01 systemd[1]: Stopped LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Feb 04 21:08:01 systemd[1]: slapd.service: Found left-over process 13994 (slapd) in control group while starting unit. Ignoring.
Feb 04 21:08:01 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Feb 04 21:08:01 systemd[1]: Starting LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)...
Feb 04 21:08:01 slapd[31422]: Starting OpenLDAP: slapd failed!
Feb 04 21:08:01 systemd[1]: slapd.service: Control process exited, code=exited, status=1/FAILURE
Feb 04 21:08:01 systemd[1]: slapd.service: Failed with result 'exit-code'.
Feb 04 21:08:01 systemd[1]: Failed to start LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Feb 04 21:08:04 systemd[1]: slapd.service: Service RestartSec=3s expired, scheduling restart.
Feb 04 21:08:04 systemd[1]: slapd.service: Scheduled restart job, restart counter is at 286.
Feb 04 21:08:04 systemd[1]: Stopped LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Feb 04 21:08:04 systemd[1]: slapd.service: Found left-over process 13994 (slapd) in control group while starting unit. Ignoring.
Feb 04 21:08:04 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Feb 04 21:08:04 systemd[1]: Starting LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)...
Feb 04 21:08:05 slapd[31434]: @(#) $OpenLDAP: slapd  (Jan 22 2021 03:54:40) $
                                      Debian OpenLDAP Maintainers <pkg-openldap-devel@lists.alioth.debian.org>
Feb 04 21:08:05 slapd[31434]: daemon: bind(8) failed errno=98 (Address already in use)
Feb 04 21:08:05 slapd[31434]: slapd stopped.
Feb 04 21:08:05 slapd[31434]: connections_destroy: nothing to destroy.
Feb 04 21:08:05 slapd[31429]: Starting OpenLDAP: slapd failed!
Feb 04 21:08:05 systemd[1]: slapd.service: Control process exited, code=exited, status=1/FAILURE
Feb 04 21:08:05 systemd[1]: slapd.service: Failed with result 'exit-code'.
Feb 04 21:08:05 systemd[1]: Failed to start LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Feb 04 21:08:08 systemd[1]: slapd.service: Service RestartSec=3s expired, scheduling restart.
Feb 04 21:08:08 systemd[1]: slapd.service: Scheduled restart job, restart counter is at 287.
Feb 04 21:08:08 systemd[1]: Stopped LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Feb 04 21:08:08 systemd[1]: slapd.service: Found left-over process 13994 (slapd) in control group while starting unit. Ignoring.
Feb 04 21:08:08 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Feb 04 21:08:08 systemd[1]: Starting LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)...
Feb 04 21:08:08 slapd[31441]: @(#) $OpenLDAP: slapd  (Jan 22 2021 03:54:40) $
                                      Debian OpenLDAP Maintainers <pkg-openldap-devel@lists.alioth.debian.org>
Feb 04 21:08:08 slapd[31441]: daemon: bind(8) failed errno=98 (Address already in use)
Feb 04 21:08:08 slapd[31441]: slapd stopped.
Feb 04 21:08:08 slapd[31441]: connections_destroy: nothing to destroy.
Feb 04 21:08:08 slapd[31436]: Starting OpenLDAP: slapd failed!
Feb 04 21:08:08 systemd[1]: slapd.service: Control process exited, code=exited, status=1/FAILURE
Feb 04 21:08:08 systemd[1]: slapd.service: Failed with result 'exit-code'.
Feb 04 21:08:08 systemd[1]: Failed to start LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).

Thank’s for your help :slight_smile:

1 Like

Sounds like there’s already something using slapd’s port on the system … Not sure how this happened …

Possibly we can try to check what process with

netstat -tulpn | grep 389

Also maybe that’s another slapd service for some reason, so maybe let’s try to

pkill slapd

then attempt to re-restart the service :

systemctl restart slapd
3 Likes

Hello Aleks,

thanks for your help.

After killing the service and restart everything seems to work fine :slight_smile:

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.