Ubuntu
openldap package

slapd does not automatically restart on failure

Bug #1838380 reported by Kseniya Blashchuk
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openldap (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Slapd does not restart after a failure. Slapd package does not include
systemd unit file at all, only init.d script. Makes sense to make a
unitfile with a Restart=on-failure option.

$ lsb_release -rd
Description: Ubuntu 16.04.5 LTS
Release: 16.04

$ apt-cache policy slapd
slapd:
  Installed: 2.4.42+dfsg-2ubuntu3.3
  Candidate: 2.4.42+dfsg-2ubuntu3.5
  Version table:
     2.4.42+dfsg-2ubuntu3.5 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
 *** 2.4.42+dfsg-2ubuntu3.3 100
        100 /var/lib/dpkg/status
     2.4.42+dfsg-2ubuntu3.2 500
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
     2.4.42+dfsg-2ubuntu3 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  affects ubuntu/openldap

Revision history for this message
Ryan Tandy (rtandy) wrote : Re: [Bug 1838380] [NEW] slapd does not automatically restart on failure

Hello,

You can configure that yourself with a systemd drop-in file that
modifies the generated unit. A similar one was recently added to set
RemainOnExit=false; see bug 1821343.

I can't comment on whether it's appropriate to add that behaviour in the
package by default.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openldap (Ubuntu):
status: New → Confirmed
Revision history for this message
Kseniya Blashchuk (ksyblast) wrote :

Obviously, it's possible to configure it, however I guess it's better to include it to a package rather than everybody would need to do it manually. In my opinion that would help to avoid service interruptions.

Revision history for this message
Robie Basak (racb) wrote :

Also see bug 1821927.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I think a database-like service having such a restart configuration should be a local decision by each administrator. I fear data could be corrupted, for example, if the crash was caused by a bug, and further restarts could make the problem worse.

What I do agree with is that openldap should migrate to a systemd service, away from sysv.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.