Problem:
Multiple instances of "/usr/share/centrifydc/bin/nscdrestart.sh flush" are executing. The processes can be seen when performing a ps command. The output is similar to:
root 336 0.0 0.0 11444 1580 ? S May30 0:00 /bin/bash /usr/share/centrifydc/bin/nscdrestart.sh flush
root 343 0.0 0.0 36328 588 ? S Mar16 0:00 /usr/share/centrifydc/libexec/adreload
root 351 0.0 0.0 9188 1100 ? S Mar16 0:00 /bin/bash /usr/share/centrifydc/bin/nscdrestart.sh flush
root 515 0.0 0.0 36328 596 ? S Apr16 0:00 /usr/share/centrifydc/libexec/adreload
root 520 0.0 0.0 9268 1100 ? S Apr16 0:00 /bin/bash /usr/share/centrifydc/bin/nscdrestart.sh flush
root 535 0.0 0.0 11444 1496 ? S May28 0:00 /bin/bash /usr/share/centrifydc/bin/nscdrestart.sh flush
root 537 0.0 0.0 36328 596 ? S Apr03 0:00 /usr/share/centrifydc/libexec/adreload
root 541 0.0 0.0 9268 1100 ? S Apr03 0:00 /bin/bash /usr/share/centrifydc/bin/nscdrestart.sh flush
root 564 0.0 0.0 11444 1456 ? S May29 0:00 /bin/bash /usr/share/centrifydc/bin/nscdrestart.sh flush
root 590 0.0 0.0 36328 592 ? S Apr23 0:00 /usr/share/centrifydc/libexec/adreload
Cause:
There is a background worker thread running inside adclient that will periodically run the nscdrestart script to flush NSCD. The thread runs the script by spawning a child process without waiting for its completion. The nscdrestart.sh process can also be created when adflush or daflush is run. If the nscd daemon is in a busy state or is non-responsive, the parent process terminates leaving these zombie processes behind.
Workaround:
Processes can be terminated using the "kill" command.
Disable the auto-restart of the nsdrestart.sh script by changing the permission with the following command:
# chmod -x nscdrestart.sh
Resolution:
This issue is resolved in Centrify DirectControl Suite 2017 and later.