Bug 171271
| Summary: | ldap does not start after power failure | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexey Baj <alex> |
| Component: | openldap | Assignee: | Jay Fenlason <fenlason> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | jfeeney |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-10-20 08:06:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
From Bugzilla Helper: User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.2 (like Gecko) Description of problem: After power failure there is a high probability that ldap startup script would hang or would fail but report success. To make it start again one has to either recreate databases or run db_recover -h /var/lib/ldap, THEN run slaptest as user ldap. Version-Release number of selected component (if applicable): openldap-servers-2.2.23-5 How reproducible: Sometimes Steps to Reproduce: 1. start slapd 2. press 'reset' 3. boot computer again Actual Results: boot process hangs on "Starting slapd" or . "Starting slapd [ OK ]", but slapd is not running. Expected Results: At very least, init script should not block booting, and report failure if slapd fails to start. Maybe good thing is to run db_recovery each time slapd starts. Additional info: When one manually runs db_recover $PATH_TO_LDAP_DB, then /sbin/service ldap start, in $PATH_TO_LDAP_DB files __db.* will be created with root permissions, and slapd would still not run. Cause is slaptest in init script.