sinkak wrote:i tried adding new server ip to one of the clients nrpe.cfg file. That removed the error.
This means it's running daemonized and is why we needed to see the output of `ps -ef | grep nrpe.cfg` - the changes you maded to your inetd.conf file were of no use.
sinkak wrote:i have more than 100 hosts. i cant edit on each client.
Is there any thing i can do like that on server side so that it changes all clients config file?
Short of assuming the old IP - No.
Now would be a good time to implement some sort of centralized management of your configs though. To a lesser extent you could prevent this one small problem from happening again in the future by using a DNS name instead of an IP.
sinkak wrote:ubuntu@ip:~$ grep nrpe /etc/xinetd.d/nrpe
service nrpe
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
Run from inetd
If it's daemonized though, the inetd variant will fail to launch because 5666 is already in use. It would appear you're using both, but daemonized wins which means the necessary changes are allowed_hosts in nrpe.cfg.
if i add new server IP individually to client nrpe.cfg file then no error.
But i cant do the same for 100 client hosts. I am trying to solve this error from server side.
I've already answered this. It's not the answer I want to give you, but it is the ONLY answer.
sinkak wrote:i have more than 100 hosts. i cant edit on each client. Is there any thing i can do like that on server side so that it changes all clients config file?
jdalrymple wrote:Short of assuming the old IP - No.
Now would be a good time to implement some sort of centralized management of your configs though. To a lesser extent you could prevent this one small problem from happening again in the future by using a DNS name instead of an IP.