Last Modified: Jun 30, 2021
See more info
Known Affected Versions:
14.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.1.2, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.3, 184.108.40.206, 14.1.4, 220.127.116.11, 18.104.22.168, 22.214.171.124
Opened: Dec 03, 2019
If the system daemon responsible for LDAP authentication crashes, the system will not automatically restart it, and remote LDAP authentication may stop working. In /var/log/daemon.log, you may see the following: warning systemd: nslcd.service failed
System authentication stops working until nslcd is restarted.
Nslcd daemon crashed, and it fails to restart.
Manually restart nslcd daemon: tmsh start sys service nslcd nslcd can be reconfigured to restart automatically and create core files when it crashes, though these changes will be lost across software installs (and is not backed up as part of a UCS archive): 1. Run "systemctl edit nslcd", which will open a text editor (by default, nano). 2. In the text editor, add these contents: [Service] # Allow core files LimitCORE=infinity # Try to keep auth daemon running, even if it crashes Restart=always 3. Exit the text editor and save the file 4. Check the output of "systemctl status nslcd" for any warnings/errors from systemd as a result of editing the file; there should not be any. 5. Restart nslcd: systemctl restart nslcd