Last Modified: Apr 05, 2023
Known Affected Versions:
F5OS-A 1.1.0, F5OS-A 1.1.1
F5OS-A 1.4.0, F5OS-A 1.3.0
Opened: Aug 18, 2022 Severity: 3-Major
The script that watches and restarts the nslcd process could sometimes fail to do so, and would sometimes log messages that appeared alarming.
The messages were benign, but the occasional failure to restart nslcd on config change could cause authentication changes to fail to propagate to the running process.
Changing authentication settings that affect nslcd.
Restarting the name-service-ldap container is likely to solve the issue.
The nslcd start/run script was rewritten to minimize alarming log messages and reliably start and restart the process when expected.