Bug 946921
| Summary: | slapd fails to start on boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bojan Smojver <bojan> |
| Component: | openldap | Assignee: | Jan Synacek <jsynacek> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | jsynacek, jv+fedora, phracek, rmeggins |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-04-20 19:26:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bojan Smojver
2013-04-01 01:12:15 UTC
Hmm, interestingly, downgrade to 2.4.33-3 also gives the same result. Something else must be tripping up slapd on boot... It is probably related to network not being available when slapd is fired up: -------------------- Apr 01 12:13:47 host slapd[759]: @(#) $OpenLDAP: slapd 2.4.33 (Oct 31 2012 12:01:33) $ Apr 01 12:13:47 host slapd[759]: daemon: bind(8) failed errno=99 (Cannot assign requested address) Apr 01 12:13:47 host slapd[759]: slapd stopped. Apr 01 12:13:47 host slapd[759]: connections_destroy: nothing to destroy. Apr 01 12:13:47 host systemd[1]: slapd.service: control process exited, code=exited status=1 Apr 01 12:13:48 host systemd[1]: Unit slapd.service entered failed state -------------------- My /etc/sysconfig/slapd has: -------------------- SLAPD_URLS="ldap://127.0.0.1/ ldap://<private IP>/ ldaps://127.0.0.1 ldaps://<private IP>/" -------------------- Shouldn't slapd service require network to be up by default? Adding network.target to the service file make it come up properly. In other words: After=syslog.target network.target openldap-2.4.35-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/openldap-2.4.35-1.fc19 Pushed: http://pkgs.fedoraproject.org/cgit/openldap.git/commit/?id=645d16ca6127af11c0b42f88d9317f84633c671c openldap-2.4.35-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/openldap-2.4.35-1.fc18 Package openldap-2.4.35-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openldap-2.4.35-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4752/openldap-2.4.35-1.fc19 then log in and leave karma (feedback). openldap-2.4.35-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/openldap-2.4.35-3.fc18 openldap-2.4.35-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. openldap-2.4.35-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |