Oct 13 14:06:55 client nrpe[4027]: Server listening on 127.0.0.1 port 5666. If the server is listening on the localhost IP address (127.0.0.1), it will only be able to accept connections on port 5666 …

For my specific case, there is supposed to be an nrpe daemon (opsview install) listening on port 5666, but there is no nrpe daemon running. If I try to start it, it exits immediately. lsof -i :5666 …

2015年6月22日 · By default, the NRPE daemon listens on TCP port 5666, whether it's configured to do SSL or not.

2024年10月29日 · The web application listens on port 80 inside the container, that I forward to 5665 host port. The nginx reverse proxy listens on port 5666 and forwards the requests to the …

2016年5月4日 · There is a rule in the firewall who permitt connexion from 10.1.1.232 on the 5666 port. From 10.1.1.232 :

2021年4月12日 · I have already checked some docs from here, but still coundt find the solution. I have a nagios server and a webserver to be monitored (RAM). Debian both Server and …

2012年8月23日 · I literally compared the nrpe.cfg between both, definitely had the IP for allowed host, and all plugins were rsync'd, permissions were all the same. One problem I had was …

The port I am trying to allow is 5666. If I disable the firewall on the destination machine, I can connect, so I know it is a firewall issue. I have added the rule with: iptables -N NRPE. iptables …

2011年10月20日 · From the server I was able to confirm it was not a firewall issue, could telnet to the 5666 port, could run a blanket check_nrpe and get the status as a return value. Could run …

On server side: First make sure port 5666 is running $ netstat -ntlp tcp 0 0 0.0.0.0:5666 0.0.0.0:*** If running then the problem is in your client machine. On the client side: inside nrpe.conf …