Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47394

When removing the last instance of 389, we should clean up /var/lock/dirsrv, and maybe other directories like this(/var/run/dirsrv, etc), because if you create a DS instance running as a different user than the previous instance, these "old" directories remain, and prevent a new server instance from being created.

To reproduce:

[1] run setup-ds.pl and specify "nobody" as the user and group for the server instance.
[2] run remove-ds.pl
[3] Create a user and group called "dirsrv"
[4] run setup.pl and specify "dirsrv" as the user and group
[5] setup fails.

$ rpm -qa  | grep 389
389-ds-base-1.3.3.1-9.el7.x86_64
389-ds-base-debuginfo-1.3.3.1-9.el7.x86_64
389-ds-base-libs-1.3.3.1-9.el7.x86_64

$ sudo setup-ds.pl -s -f template_nobody.inf 
Your new DS instance 'rhel7ds' was successfully created.
Exiting . . .
Log file is '/tmp/setup5SUXDV.log'

$ ls -l /var/lock/ | grep dirsrv
drwxrwx---. 3 nobody nobody 60 Dec 10 15:44 dirsrv
$ sudo remove-ds.pl -i slapd-rhel7ds
Instance slapd-rhel7ds removed.

$ ls -l /var/lock | grep dirsrv
$ echo $?
1
$ sudo setup-ds.pl -s -f template_dirsrv.inf 
Your new DS instance 'rhel7ds' was successfully created.
Exiting . . .
Log file is '/tmp/setupyK7yW2.log'

$ ls -l /var/lock/ | grep dirsrv
drwxrwx---. 3 dirsrv  dirsrv    26 Dec 10 15:47 dirsrv

Instance was successfully installed. Marking as VERIFIED.

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.

https://rhn.redhat.com/errata/RHSA-2015-0416.html