Bug 30610 – Database check during slapd start may cause the system to hang at boot

Bug 30610 - Database check during slapd start may cause the system to hang at boot


Summary:	Database check during slapd start may cause the system to hang at boot

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-02-28 10:55 CET by Janis Meybohm
Modified:	2018-04-14 13:43 CEST (History)
CC List:	1 user (show)

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 Janis Meybohm

2013-02-28 10:55:26 CET

<http://forum.univention.de/viewtopic.php?f=48&t=2391>

In some cases the slapd database check may cause the system not to boot because the slapd init script hangs forever after printing "Check database: ..."

We should watch over the db*_stat, db*_recover commands and kill them if their running to long.

Comment 1 Stefan Gohmann

2017-06-16 20:40:11 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 2 Stefan Gohmann

2017-08-08 07:09:41 CEST

This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.