Nagios Support Forum

Not a one. I'm good.

I did reset the password with no problems. I set it to the original password according to my records. As far as I can tell, it was locked because of too many wrong authentication attempts.

Are there any repercussions to resetting the Nagios user password? I don't mean nagiosadmin, but nagios. We're unable to logon locally and the local password is locked.

Fixed it. Had to add the new eth1 to accept http traffic.

iptables -I INPUT 5 -i eth1 -p tcp --dport 80 -m state --state NEW,ESTABLISHED -j ACCEPT

I have restarted httpd. I'm connecting to the same IP. I configured the new eth manually with the same settings.

# service httpd status
httpd (pid 7875) is running...

Well I got Nagios connecting to the monitored servers again. Hyper-V had changed the ethernet connection to a different adapter with a different mac address. Once I gave the new eth1 a static IP, the services recovered. I can connect with ssh, but still no web interface.

Our Hyper-V environment rebooted the guests early this morning. Nagios was one of the VMs. Now Nagios is sending hundreds of could not fetch information from server alerts. The config verified, but I can't login to the web interface or via putty (ssh).

I got it. I removed the iftraffic_if23_10.xx.xx.xx file from /tmp. Since I ran the command manually as root, the console could not overwrite the file.

According to the snmpwalk, the production ehternet is ifalias.23. When I run the command manually, it works. If I change the <server>.cfg, I get an error on the console (Return code of 13 is out of bounds). # /usr/local/nagios/libexec/check_snmp_ifstatus.pl -H 10.xx.xx.xx -C publicxxxxxxx -v 2 -i &q...