Warning threshold must be float or float triplet!

[Marc Powell]

These could be normal. Nagios will spawn a child process to manage each
check. What you're interested in is if there are multiple nagios process
with a parent PID of 1. ps -ef usually shows child/parent PIDS. If you
stop nagios and see none remaining then you don't have multiple daemons
running.

As far as reloading config, a HUP to the parent process or calling
'/etc/init.d/nagios reload' is sufficient.

--
Marc

> -----Original Message-----
> From: Justin Craig [mailto:jrcraig.email at gmail.com]
> Sent: Wednesday, August 02, 2006 12:10 PM
> To: Marc Powell
> Cc: Nagios Users Mailinglist
> Subject: Re: [Nagios-users] Warning threshold must be float or float
> triplet! 
> 
> 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 204.64.105.21
> 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 192.168.146.5 -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 192.168.170.5
> 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 204.64.191.5 -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 192.168.146.5
> nagios    6164  0.0  0.0  1700  544 ?        S    11:57   0:00
/bin/ping -
> n -U -w 10 -c 5 204.64.191.5
> 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 204.64.105.21
> 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 192.168.146.5 -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 192.168.170.5
> 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 204.64.191.5 -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 192.168.146.5
> nagios    6164  0.0  0.0  1700  544 ?        S    11:57   0:00
/bin/ping -
> n -U -w 10 -c 5 204.64.191.5
> 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?
> 
> On 8/2/06, Marc Powell <marc at ena.com> wrote:
> 
> 
> 
> 	> -----Original Message-----
> 	> From: Justin Craig [mailto: jrcraig.email at gmail.com
> <mailto:jrcraig.email at gmail.com> ]
> 	> 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: nagios-users-bounces at lists.sourceforge.net
> <mailto:nagios-users-bounces at lists.sourceforge.net>
> 	[mailto:nagios-
> 	> users-
> 	>       > bounces at lists.sourceforge.net
> <mailto:bounces at lists.sourceforge.net> ] 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
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null