Systhread: "With ICMP off it can be difficult to configure tools like Nagios for simple up and down checks. In this text getting around the no ICMP problem and a script to handle it for Nagios."
on 08/16/2010 – Made popular on 08/16/2010
Sometimes a system administrator needs to get around a few rules that are in place for good (or not) reasons. One example is when networks have ICMP turned off (or even just a portion of it). With ICMP off it can be difficult to configure tools like Nagios for simple up and down checks.
I have a nagios install on CentOS that has been working away fine for the last year and a half. Today I login successfully however get the Internal Server Error and can't navigate anywhere. Same for nconf which is also installed
I've looked through past threads here on the issue, most seem to be from fresh installs, SELinux is already disabled.
I have configure nagios server and client on my lab machines which are running under VMWARE.
Now i would like to know how the nagios working in my systems. For that, what i did is i filled up the / partition with some data above 95% in client. But still it is report good status report in disk paramater in nagios server about client.
My production servers are kept at US east coast and some of the supporting apps are kept at Amsterdam in Europe. There is a Nagios instance running at US east coast as well which does a few port checks and a few checks via ssh.
Problem is that almost every day I observe packet drops using mtr (combo of traceroute and ping) as well as minor service issues which lasts for about 1 minute.
I spent hours trying to make nagios send email notification.
my contact configuration is quite simple : I juste have one : nagiosadmin, and he is the default contact.
In /var/log/nagios.log, nagios tend to send email, so it's not a matter of contact configuration.
When I copy paste the command found in the log file in the console, the mail is sent and I received it.