Univention Bugzilla – Bug 45414
nagios CRITICAL: Unknown program "<PROG>": bound to nscd socket.
Last modified: 2019-08-29 12:24:15 CEST
At least two cases have been reported about the nagios nscd message: nagios CRITICAL: Unknown program "<PROG>": bound to nscd socket. Ticket #2017091521000662 and https://help.univention.com/t/unknown-program-kopano-spooler-bound-to-nscd-socket/6551 After restarting the nscd process the error is gone.
The message has been introduced with Bug #42812.
I think we should fix it soon since it is a regression.
Workaround: restart nscd or remove UNIVENTION_NSCD2 from the list of nagios services for the server object in UMC and add UNIVENTION_NSCD.
Commit: e837a1350ba6a05bf23308b3af2dc6d71c0d2a28 Package: univention-nagios Version: 10.1.1-2A~4.2.0.201709211123 Branch: ucs_4.2-0 Scope: errata4.2-2 I used lsof to check which program opened the nscd socket. lsof sometimes returns the wrong result. The problem occurs if a program deletes the file which was created during the socket generation but does not close the socket. That case is handled wrong by lsof and sometimes these programs are reported on the wrong sockets. Small script to illustrate the problem: ''' #!/bin/bash for i in $(seq 1 1024); do ( nc -l -U "$PWD/test_soc"$i & ) done sleep 1 for i in $(seq 1 1024); do rm "test_soc$i" done sleep 1 ( nc -l -U "$PWD/test_soc" & ) echo lsof lsof "test_soc" echo "fuser" fuser "test_soc" pkill -f "nc -l -U $PWD/test_soc" rm "$PWD/test_soc ''' I fixed it by replacing lsof with fuser.
OK - nscd check OK - YAML
<http://errata.software-univention.de/ucs/4.2/193.html>