Marc, As you said, correct. I have multiple nagios daemons running on the host. How do I get rid of this? I tried, killall -9 nagios service nagios start [root@lnx-nagios local]# ps -ef | grep nagios nagios 2672 1 0 19:23 ? 00:00:01 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 5127 1 0 19:25 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 5128 5127 0 19:25 ? 00:00:00 /usr/local/nagios/libexec/check_ping -H 10.193.50.60 -w 100.0,20% -c 500.0,60% -p 5 nagios 5129 5128 0 19:25 ? 00:00:00 /bin/ping -n -U -w 10 -c 5 10.193.50.60 nagios 5131 1 0 19:25 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 5132 5131 0 19:25 ? 00:00:00 /usr/local/nagios/libexec/check_ping -H 10.130.131.241 -w 100.0,20% -c 500.0,60% -p 5 nagios 5133 5132 0 19:25 ? 00:00:00 /bin/ping -n -U -w 10 -c 5 10.130.131.241 nagios 5138 1 0 19:25 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 5139 5138 0 19:25 ? 00:00:00 /usr/local/nagios/libexec/check_ping -H 10.193.50.140 -w 100.0,20% -c 500.0,60% -p 5 nagios 5141 5139 0 19:25 ? 00:00:00 /bin/ping -n -U -w 10 -c 5 10.193.50.140 nagios 5142 1 0 19:25 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 5143 5142 0 19:25 ? 00:00:00 /usr/local/nagios/libexec/check_ping -H 10.30.8.221 -w 100.0,20% -c 500.0,60% -p 5 nagios 5144 5143 0 19:25 ? 00:00:00 /bin/ping -n -U -w 10 -c 5 10.30.8.221 nagios 5149 1 0 19:25 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 5150 5149 0 19:25 ? 00:00:00 /usr/local/nagios/libexec/check_nrpe -H 172.16.17.188 -c check_users nagios 5158 1 0 19:25 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 5159 5158 0 19:25 ? 00:00:00 /usr/local/nagios/libexec/check_ping -H 172.16.17.15 -w 3000.0,80% -c 5000.0,100% -p 5 nagios 5160 5159 0 19:25 ? 00:00:00 /bin/ping -n -U -w 30 -c 5 172.16.17.15 nagios 5169 1 0 19:25 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 5170 5169 0 19:25 ? 00:00:00 /usr/local/nagios/libexec/check_nrpe -H 172.16.17.128 -c check_load root 5178 3535 0 19:25 pts/0 00:00:00 grep nagios still have the multiple deamons running? Any help on this would be appreciated. Thanks -shankar <div class="gmail_quote">On Thu, Jul 23, 2009 at 5:34 PM, Marc Powell <<a href="mailto:marc@ena.com">marc@ena.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"> On Jul 23, 2009, at 6:28 AM, <a href="mailto:asam30@gmail.com">asam30@gmail.com</a> wrote: > Hi All, > > I am using check_ping to checking the status of server (up or down). > we have two nagios servers (one at production site, USA and another > one at DEV site, India). I am now monitoring some of the network > devices (using ping) resides at USA from Nagios server located in > India. All I am getting is </div><div class="im">> PING WARNING - Packet loss = 0%, RTA = 268.97 > > I am always getting warning message, since the RTA time would be > normally (on WAN) 268.97ms. > > I did even changed the parameters in check_command, but still does > not work. > > check_command check_ping!500.0,20%!900.0,60% > > Can someone please give any solution for this? </div>If you've changed the WARNING threshold to 500 or higher and still see warnings for lower numbers, I'd say you most likely didn't restart nagios to have your changes take effect or you have multiple nagios daemons running at the same time. -- Marc ------------------------------------------------------------------------------ _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote></div> -- Shankar Asam