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://pagure.io/389-ds-base/issue/50989

#### Issue Description
[27/Mar/2020:01:29:27.766580532 +0000] - INFO - Security Initialization - slapd_ssl_init2 - Configured SSL version range: min: TLS1.2, max: TLS1.3
[27/Mar/2020:01:29:27.769148822 +0000] - INFO - Security Initialization - slapd_ssl_init2 - NSS adjusted SSL version range: min: TLS1.2, max: TLS1.3
[27/Mar/2020:01:29:27.770667035 +0000] - ERR - add_new_slapd_process - Unable to start slapd because it is already running as process 7
[27/Mar/2020:01:29:27.771824337 +0000] - CRIT - main - Shutting down due to possible conflicts with other slapd processes


#### Package Version and Platform
1.4.3.4 389ds container


I think that this is caused by a failure to clean /run/lock on shutdown of the container - either we are terminating the process incorrectly (which I don't think we are, the DB is clean on startup), or we aren't properly purging the lock files, expecting a new pid to exist or similar. I'll need to investigate more, as this causes spurious startup failures in my production ldap environment.

This does not apply to RHEL, closing...