okay i modified checkcommands.cfg to reflect what you noted here. I also did a ps axu | grep nagios and AGAIN there are multiple instances running. here is the output: nagios 6155 0.0 0.0 1700 536 ? S 11:57 0:00 /bin/ping -n -U -w 10 -c 5 <a href="http://204.64.105.21">204.64.105.21</a> nagios 6157 0.0 0.2 23900 1464 ? S 11:57 0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 6158 0.5 0.1 5612 1036 ? S 11:57 0:00 /usr/local/nagios/libexec/check_ping -H <a href="http://192.168.146.5">192.168.146.5</a> -w 100.0,20% -c 500.0,60% -p 5 nagios 6160 0.0 0.0 1700 540 ? S 11:57 0:00 /bin/ping -n -U -w 10 -c 5 <a href="http://192.168.170.5">192.168.170.5</a> nagios 6161 0.0 0.2 23900 1464 ? S 11:57 0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 6162 0.5 0.1 5612 1036 ? S 11:57 0:00 /usr/local/nagios/libexec/check_ping -H <a href="http://204.64.191.5">204.64.191.5</a> -w 100.0,20% -c 500.0,60% -p 5 nagios 6163 0.0 0.0 1700 536 ? S 11:57 0:00 /bin/ping -n -U -w 10 -c 5 <a href="http://192.168.146.5">192.168.146.5</a> nagios 6164 0.0 0.0 1700 544 ? S 11:57 0:00 /bin/ping -n -U -w 10 -c 5 <a href="http://204.64.191.5">204.64.191.5</a> root 6166 0.0 0.1 3720 676 pts/2 R+ 11:57 0:00 grep nagios nagios 6155 0.0 0.0 1700 536 ? S 11:57 0:00 /bin/ping -n -U -w 10 -c 5 <a href="http://204.64.105.21">204.64.105.21</a> nagios 6157 0.0 0.2 23900 1464 ? S 11:57 0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 6158 0.5 0.1 5612 1036 ? S 11:57 0:00 /usr/local/nagios/libexec/check_ping -H <a href="http://192.168.146.5">192.168.146.5</a> -w 100.0,20% -c 500.0,60% -p 5 nagios 6160 0.0 0.0 1700 540 ? S 11:57 0:00 /bin/ping -n -U -w 10 -c 5 <a href="http://192.168.170.5">192.168.170.5</a> nagios 6161 0.0 0.2 23900 1464 ? S 11:57 0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg nagios 6162 0.5 0.1 5612 1036 ? S 11:57 0:00 /usr/local/nagios/libexec/check_ping -H <a href="http://204.64.191.5">204.64.191.5</a> -w 100.0,20% -c 500.0,60% -p 5 nagios 6163 0.0 0.0 1700 536 ? S 11:57 0:00 /bin/ping -n -U -w 10 -c 5 <a href="http://192.168.146.5">192.168.146.5</a> nagios 6164 0.0 0.0 1700 544 ? S 11:57 0:00 /bin/ping -n -U -w 10 -c 5 <a href="http://204.64.191.5">204.64.191.5</a> root 6166 0.0 0.1 3720 676 pts/2 R+ 11:57 0:00 grep nagios When stopping Nagios, I typically issue a /etc/rc.d/init.d stop and then verify there are none running. I also use Kill -HUP since I normally start nagios as a daemon with the -d. Is this the correct process? Further, what is best practices after adding a host to refresh Nagio to pick up that host without reflecting undetermined availability for the rest of the hosts or causing any problems? <div>On 8/2/06, Marc Powell <<a href="mailto:marc@ena.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">marc@ena.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"> > -----Original Message----- > From: Justin Craig [mailto:<a href="mailto:jrcraig.email@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> jrcraig.email@gmail.com</a>] > Sent: Wednesday, August 02, 2006 8:38 AM > To: Marc Powell > Cc: Nagios Users Mailinglist > Subject: Re: [Nagios-users] Warning threshold must be float or float > triplet! > > In my checkcommands.cfg for this host in question, I have: > > # 'check_local_load' command definition > define command{ > command_name check_local_load > command_line $USER1$/check_load -w $ARG1$ -c $ARG2$ > } > Yes, that looks good. I'd -- - verify that nagios was reloaded after creating this command definition - verify that there aren't multiple nagios daemons running (stop; kill; start) - verify that nagios is executing the command I think is. Modify command_line to be the following then check the contents of /tmp/nagios -- command_line /bin/echo "$USER1$/check_load -w $ARG1$ -c $ARG2$" >> /tmp/nagios -- Marc > > -----Original Message----- > > From: <a href="mailto:nagios-users-bounces@lists.sourceforge.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> nagios-users-bounces@lists.sourceforge.net </a> [mailto:<a href="mailto:nagios-" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">nagios-</a> > users- > > <a href="mailto:bounces@lists.sourceforge.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> bounces@lists.sourceforge.net</a>] On Behalf Of Justin Craig > > Sent: Tuesday, August 01, 2006 2:41 PM [chop] > > check_command > > check_local_load!5.0,4.0,3.0!10.0,6.0,4.0 > > } ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash <a href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">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> -- - Justin