Warning threshold must be float or float triplet

[Joe Morris]

On Fri, 5 Sep 2003, Achim Altmann wrote:

| sorry, now run my check_load with the correct syntax but the folling message
| comes up
|
| Warning threshold must be float or float triplet
|
| i have that lines
| define service{
|         use                             generic-service         ; Name of
| service template to use
|         host_name                       test.domain.com
| service_description             load
|         is_volatile                     0
|         check_period                    24x7
|         max_check_attempts              3
|         normal_check_interval           5
|         retry_check_interval            1
|         contact_groups                  linux-admins
|         notification_interval           120
|         notification_period             24x7
|         notification_options            c,r
|         check_command                   check_load!-w WLOAD1,WLOAD5,WLOAD15!-c
| CLOAD1,CLOAD5,CLOAD15
|         }
|
|
| and in checkcommands.cfg
|
| # 'check_load' command definition
| define command{
|         command_name    TEST Load
|         command_line    $USER1$/check_load -w $ARG1$ -c $ARG2$
|         }

Whoa, that won't work.  You defined the command_name as "TEST load".  This
is the name that entries in our services.cfg will reference.  Change that
to read check_load, then your services.cfg can reference it correctly.


_______________________________________________
Joe Morris, Web Systems Manager
Academic Technology and Networks
The University of North Carolina at Chapel Hill


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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