LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Security (https://www.linuxquestions.org/questions/linux-security-4/)
-   -   nslcd dead but subsys locked (https://www.linuxquestions.org/questions/linux-security-4/nslcd-dead-but-subsys-locked-4175650677/)

vinmansbrew 03-22-2019 09:59 AM

nslcd dead but subsys locked
 
Sooooo, working on changing nslcd.conf file to reflect change to a new ldap server.
Go to restart nslcd and it loooks ok, but a service nslcd status delivers the error: nslcd dead but subsys locked

Tried to rename the /var/run/nslcd directory and create a new one with same perms/owner/grp, and same with /var/lock/subsys/nslcd
Any thoughts on why this issue is occuring?

Rhel 6.10 running on vmware 11 (I think, though I don't think vmware is the issue as other servers are ok)

Thanks!

tyler2016 03-23-2019 05:52 AM

Did the init script successfully bring down nslcd? I agree, it probably has nothing to do with VMWare.

vinmansbrew 03-26-2019 12:32 PM

Well, stopping/starting the service would appear to work, but changes would not actually load. A pkill nslcd goes through, then a a service nslcd status, shows the nslcd dead but subsys locked error.

tyler2016 03-27-2019 05:24 AM

nslcd dead but subsys locked isn't generated by nslcd, but by the init script's status function. It just means there is a pid file but the process isn't running. Try killing nslcd and running it in debug mode.

Code:

# service nslcd stop
Stopping nslcd:                                            [  OK  ]
# ps -ef | grep nslcd
root      1487  1381  0 06:23 pts/0    00:00:00 grep nslcd
# nslcd -d
nslcd: DEBUG: add_uri(ldap://127.0.0.1/)
nslcd: version 0.7.5 starting
nslcd: DEBUG: unlink() of /var/run/nslcd/socket failed (ignored): No such file or directory
nslcd: DEBUG: setgroups(0,NULL) done
nslcd: DEBUG: setgid(55) done
nslcd: DEBUG: setuid(65) done
nslcd: accepting connections


vinmansbrew 03-27-2019 09:22 AM

Well, debug mode didn't really point out anything, but it caused me to recheck selinux and find a typo in the boolean. Always with the selinux!

Thanks for the assist!


All times are GMT -5. The time now is 10:39 PM.