Bug 54798 – Leftover slapd process if import of failed.ldif failed - cannot be restarted

Bug 54798 - Leftover slapd process if import of failed.ldif failed - cannot be restarted


Summary:	Leftover slapd process if import of failed.ldif failed - cannot be restarted

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2022-05-25 14:36 CEST by Julia Bremer
Modified:	2022-05-25 14:36 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Julia Bremer

2022-05-25 14:36:41 CEST

When a failed.ldif exists on the system, slapd tries to import it during startup. 

If this goes wrong, either because the import failed, or because of a timeout, 
the slapd process will survive even though the startup failed. Systemd recognizes slapd as failed at startup and thus doesn't kill the process.
 
A restart of the slapd is then not possible any more because "slapd is still running". Only after killing the leftover process, it is possible to restart it normally again.