[Nagiosplug-help] check_ping problem

[Andreas Ericsson]

Mike Feetham wrote:
> Brian,
> 
> I'm having the exact same issue (SuSE Enterprise).  If enough of the
> check_ping commands build up they will stop other checks from processing to
> the point where Nagios will start alerting you that EVERYTHING is down.  I
> have tried explicitly specifying timeouts for the ping command but that
> doesn't seem to help.  If I find any more information I will post it.
> 
> Anyone else having this issue?
> 
> p.s. In the mean time, I wrote a quick script to kill large groups these
> pings.  Run the script with the IP or FQDN (whichever is used with the ping
> command) to wipe out all check_ping instances for that object.
> 

Or try the check_icmp plugin, which kills itself after a predefined 
amount ot time. Very nifty.

> i.e.  if I run ps -ef | grep nagios (to list all processes run by the
> Nagios) and a large number of these Check_ping commands come up for IP
> 10.10.10.2, then I would run the script:   ./kill-ping.sh 10.10.10.2
> 
> 
> 
> #!/bin/sh
> for i in `ps -ef|grep $1 |grep -v grep|awk '{print $2}'`
> {
>  kill $i
>  echo "Kill $i\007 !! Bye Bye :-)\n"
> }
> #exit 0
> 
> 
> Mike Feetham 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
> 

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer