Page 1 of 1
could not fetch information from server
Posted: Thu Mar 27, 2014 9:18 am
by rlevick
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).
Re: could not fetch information from server
Posted: Thu Mar 27, 2014 9:56 am
by slansing
Are sshd and apache running?:
Are you using firewall rules that may have been re-set during the reboot? Or selinux definitions? Without more info on your installation, nagios version, changes like the aforementioned, it's hard to troubleshoot. Can you also provide the output of the following:
Code: Select all
tail -50 /var/log/messages
tail -50 /var/log/httpd/error_log
tail -50 /usr/local/nagios/var/nagios.log
Please wrap the output of the above in code tags that are available when you are writing your reply, next to the Bold, italics, underscore, and Quote buttons.
Re: could not fetch information from server
Posted: Thu Mar 27, 2014 10:34 am
by rlevick
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.
Re: could not fetch information from server
Posted: Thu Mar 27, 2014 10:43 am
by rlevick
# service httpd status
httpd (pid 7875) is running...
Re: could not fetch information from server
Posted: Thu Mar 27, 2014 2:51 pm
by abrist
rlevick wrote:but still no web interface.
Since the adapter/ip change, have you restarted httpd?
Are you connecting to the right ip (the new one)?
Re: could not fetch information from server
Posted: Thu Mar 27, 2014 3:12 pm
by rlevick
I have restarted httpd. I'm connecting to the same IP. I configured the new eth manually with the same settings.
Re: could not fetch information from server
Posted: Thu Mar 27, 2014 4:36 pm
by rlevick
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