wicked and other systemd services not starting up correctly.
This document (7020915) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)
dbus-daemon: nss_ldap: failed to bind to LDAP server ldap://server.domain.name:389: Can't contact LDAP server
dbus: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
systemd-logind: Failed to enable subscription: Connection timed out
Wicked, systemd-logind failed to startup.
Alternatively, it is possible to reconfigure the LDAP bind policy using YaST and add bind_policy soft option to /etc/ldap.conf
In such default configuration, LDAP will continue to try and open a connection to the LDAP server until it eventually times out and fails.
During this process DBus daemon fails to register many services and in turn leads to logind and systemd being unable to register with the system bus.
Specifies the policy to use for reconnecting to an unavailable LDAP server. The default is hard_open,which reconnects if opening the connection to the directory server failed. By contrast, hard_initreconnects if initializing the connection failed. Initializing may not actually contact the directory server, and it is possible that a malformed configuration file will trigger reconnection. If soft is specified, then nss_ldap will return immediately on server failure. All "hard" reconnect policies block with exponential backoff before retrying.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7020915
- Creation Date:14-JUN-17
- Modified Date:04-JUL-17
- SUSESUSE Linux Enterprise Server
Did this document solve your problem? Provide Feedback< Back to Support Search