RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1210842 - Add PIDFile option to systemd service file
Summary: Add PIDFile option to systemd service file
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
: 1210853 (view as bug list)
Depends On: 1333198
TreeView+ depends on / blocked
Reported: 2015-04-10 17:01 UTC by Noriko Hosoi
Modified: 2020-09-13 21:16 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-11-03 20:35:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1282 0 None None None 2020-09-13 21:16:05 UTC
Red Hat Product Errata RHSA-2016:2594 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2016-11-03 12:11:08 UTC

Description Noriko Hosoi 2015-04-10 17:01:26 UTC
When stopping a dirsrv service, systemd currently guesses the PID to wait on. To make it explicit, a line like this should be added to `/usr/lib/systemd/system/dirsrv@.service`:

Comment 1 Viktor Ashirov 2015-04-20 21:01:01 UTC
*** Bug 1210853 has been marked as a duplicate of this bug. ***

Comment 6 Punit Kundal 2016-07-01 09:14:41 UTC
RHEL 7.3 x86_64

DS builds:
[root@ds ~]# rpm -qa | grep 389
Steps performed
1. Created three standalone ds instances named 'ds', 'ds2' and 'ds3'
2. Verified whether the relevant pid files are created in /var/run/dirsrv directory
[root@ds ~]# ll /var/run/dirsrv/
total 24
-rw-r--r--. 1 dirsrv dirsrv    5 Jul  1 14:04 slapd-ds2.pid
-rw-r--r--. 1 dirsrv dirsrv 2088 Jul  1 14:04 slapd-ds2.stats
-rw-r--r--. 1 dirsrv dirsrv    6 Jul  1 14:10 slapd-ds3.pid
-rw-r--r--. 1 dirsrv dirsrv 2088 Jul  1 14:10 slapd-ds3.stats
-rw-r--r--. 1 dirsrv dirsrv    5 Jul  1 13:26 slapd-ds.pid
-rw-r--r--. 1 dirsrv dirsrv 2088 Jul  1 13:26 slapd-ds.stats
3. Checked the pid of all active instances with status-dirsrv
Instance slapd-ds
[root@ds ~]# status-dirsrv ds
● dirsrv - 389 Directory Server ds.
   Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2016-07-01 14:22:26 IST; 3min 24s ago
 Main PID: 10875 (ns-slapd)
Verified pid for slapd-ds
[root@ds ~]# cat /var/run/dirsrv/slapd-ds.pid
Instance slapd-ds2
[root@ds ~]# status-dirsrv ds2
● dirsrv - 389 Directory Server ds2.
   Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2016-07-01 14:22:27 IST; 4min 33s ago
 Main PID: 10973 (ns-slapd)
Verified pid for slapd-ds2
[root@ds ~]# cat /var/run/dirsrv/slapd-ds2.pid
Instance slapd-ds3
[root@ds ~]# status-dirsrv ds3
● dirsrv - 389 Directory Server ds3.
   Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2016-07-01 14:22:27 IST; 5min ago
 Main PID: 11083 (ns-slapd)
Verified pid for slapd-ds3
[root@ds ~]# cat /var/run/dirsrv/slapd-ds3.pid
As can be seen, all the pid's match
4. Stopped all the running instances
[root@ds ~]# stop-dirsrv
Stopping instance "ds"
Stopping instance "ds2"
Stopping instance "ds3"
5. Verified that no pid file is present in /var/run/dirsrv
[root@ds ~]# ll /var/run/dirsrv/
total 0

Comment 8 errata-xmlrpc 2016-11-03 20:35:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.