[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
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.
https://pagure.io/389-ds-base/pull-request/50990
Metadata Update from @firstyear: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Metadata Update from @mreynolds: - Issue priority set to: normal - Issue set to the milestone: 1.4.3
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1843155
Issue linked to Bugzilla: Bug 1843155
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/4042
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.