Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

389ds container may fail to start due to existing process #4042

Closed
389-ds-bot opened this issue Sep 13, 2020 · 6 comments
Closed

389ds container may fail to start due to existing process #4042

389-ds-bot opened this issue Sep 13, 2020 · 6 comments
Labels
closed: fixed Migration flag - Issue
Milestone
1.4.3

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: 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.
@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the 1.4.3 milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

389-ds-bot commented Sep 13, 2020 •
edited

Comment from firstyear (@Firstyear) at 2020-03-30 04:40:26

#4043

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2020-03-30 04:40:27

Metadata Update from @Firstyear:

  • Custom field origin adjusted to None
  • Custom field reviewstatus adjusted to None

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-04-02 17:27:32

Metadata Update from @mreynolds389:

  • Issue priority set to: normal
  • Issue set to the milestone: 1.4.3

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2020-05-19 02:30:00

Metadata Update from @Firstyear:

  • Issue close_status updated to: fixed
  • Issue status updated to: Closed (was: Open)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-06-02 19:45:44

Metadata Update from @mreynolds389:

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-06-02 19:45:44

Issue linked to Bugzilla: Bug 1843155

@389-ds-bot 389-ds-bot mentioned this issue Sep 13, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Milestone
1.4.3
Development

No branches or pull requests
1 participant
@389-ds-bot