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 1360447 - nsslapd-workingdir is empty when ns-slapd is started by systemd
Summary: nsslapd-workingdir is empty when ns-slapd is started by systemd
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
Petr Bokoc
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-26 18:44 UTC by Viktor Ashirov
Modified: 2020-09-13 21:48 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
*nsslapd* now correctly sets its working directory A regression introduced in an earlier bug fix caused *nsslapd* to skip setting its working directory (the `nsslapd-workingdir` attribute) by default when it was started by *systemd*. This bug has been fixed and the working directory is being set during startup again.
Clone Of:
Last Closed: 2016-11-03 20:44:29 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1998 0 None None None 2020-09-13 21:48:33 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 Viktor Ashirov 2016-07-26 18:44:21 UTC
Description of problem:
nsslapd-workingdir is empty when ns-slapd is started by systemd. When ns-slapd is started manually, the attribute has value.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. start-dirsrv
2. ldapsearch -D "cn=Directory manager" -w Secret123 -b cn=config | grep ^nsslapd-workingdir

Actual results:
ldapsearch returns empty attribute
ldapsearch -D "cn=Directory manager" -w Secret123 -b cn=config | grep ^nsslapd-workingdir

Expected results:
ldapsearch -D "cn=Directory manager" -w Secret123 -b cn=config | grep ^nsslapd-workingdir
nsslapd-workingdir: /var/log/dirsrv/slapd-qeos-34

Additional info:
Bug was found by Simon Pichugin

Comment 3 Noriko Hosoi 2016-07-27 00:29:35 UTC
Upstream ticket:

Comment 5 Simon Pichugin 2016-08-22 08:20:49 UTC
Build tested:

Verification steps:
1. Install an instance
2. ldapsearch -D "cn=Directory manager" -w Secret123 -b cn=config | grep ^nsslapd-workingdir

nsslapd-workingdir: /var/log/dirsrv/slapd-standalone

Marking as verified.

Comment 7 errata-xmlrpc 2016-11-03 20:44:29 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.