ping

[Tim Palmer]

[list protocol note? - I suppose, since people *will* top post, a thread 
that is top posted should remain top posted]

A quick Google search shows you are by no means the first to run into this.
What is the ping check for? Do you want to check if linux1 is up from 
the Nagios server, or check something else from linux1? If the former, 
there's no need for it to be an nrpe check, if the later, google "nrpe 
check_ping" will bring up lots of clues, hints and discussions.

tim

Mad Unix wrote:
> i can ping the server with a name
> [root at linux2 etc]# ping linux1
> PING linux1.sdc.lan (10.5.1.31 <http://10.5.1.31>) 56(84) bytes of data.
> 64 bytes from 10.5.1.31 <http://10.5.1.31>: icmp_seq=1 ttl=64 time= 
> 0.147 ms
> 64 bytes from 10.5.1.31 <http://10.5.1.31>: icmp_seq=2 ttl=64 
> time=0.132 ms
>
> the error is starnge
> check_ping: %s: Warning threshold must be integer or percentage
>
>
>
> On Jan 2, 2008 3:03 PM, ad at heapoverflow.com 
> <mailto:ad at heapoverflow.com> <ad at heapoverflow.com 
> <mailto:ad at heapoverflow.com>> wrote:
>
>     -----BEGIN PGP SIGNED MESSAGE-----
>     Hash: SHA1
>
>     Probably because the hostname you defined in the service
>
>     host_name                       linux1
>
>     is unknown, try changing it to localhost or the correct local domain
>
>     Mad Unix wrote:
>     > it gave now check_ping: Invalid hostname/address - $ other commands
>     > work, only the ping it gave eror
>     >
>     > i changed the ping the client to
>     > command[check_local_disk]=/usr/local/nagios/libexec/check_disk -w
>     > $ARG1$ -c $ARG2$ -p $ARG3$
>     > command[check_local_users]=/usr/local/nagios/libexec/check_users -w
>     > $ARG1$ -c $ARG2$
>     > command[check_local_load]=/usr/local/nagios/libexec/check_load -w
>     > $ARG1$ -c $ARG2$
>     > command[check_local_procs]=/usr/local/nagios/libexec/check_procs -w
>     > $ARG1$ -c $ARG2$
>     > #command[check_ping]=/usr/local/nagios/libexec/check_ping -H $ARG1$
>     > -w $ARG2$ -c $ARG3$ -p 5
>     > command[check_ping]=/usr/local/nagios/libexec/check_ping -H
>     > $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5
>     >
>     > On Jan 2, 2008 2:29 PM, ad at heapoverflow.com
>     <mailto:ad at heapoverflow.com>
>     > <mailto:ad at heapoverflow.com <mailto:ad at heapoverflow.com>>
>     <ad at heapoverflow.com <mailto:ad at heapoverflow.com>
>     > <mailto:ad at heapoverflow.com <mailto:ad at heapoverflow.com>>> wrote:
>     >
>     > not sure but I think your check_ping command has an error, try
>     > changing it to
>     >
>     > //edit(based on your cfg):
>     >
>     > command[check_ping]=/usr/local/nagios/libexec/check_ping -H
>     > $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5
>     >
>     >
>     > Mad Unix wrote:
>     >> my nagios shows the following
>     >
>     >> check_ping: %s: Warning threshold must be integer or percentage!
>     >> on the server define service{ use
>     >> generic-service         ; Name of service template to use
>     >> host_name                       linux1 service_description
>     >> PING is_volatile                     0 check_period
>     >> 24x7 max_check_attempts              4 normal_check_interval
>     >> 5 retry_check_interval            1 contact_groups
>     >> admins notification_options            w,u,c,r
>     >> notification_interval           960 notification_period
>     >> 24x7 check_command check_nrpe!check_ping!100.0,20%!500.0,60% } on
>     >> the client runnig nrpe
>     >
>     >> command[check_ping]=/usr/local/nagios/libexec/check_ping -H
>     >> $ARG1$ -w $ARG2$ -c $ARG3$ -p 5
>     >
>     >> -- madunix
>     >
>     >>
>     ----------------------------------------------------------------------
>
>     >>
>     >
>     >>
>     >
>     -------------------------------------------------------------------------
>     >
>     >> This SF.net email is sponsored by: Microsoft Defy all challenges.
>     >> Microsoft(R) Visual Studio 2005.
>     >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>     >
>     >>
>     ----------------------------------------------------------------------
>
>     >>
>     >
>     >> _______________________________________________ Nagios-users
>     >> mailing list Nagios-users at lists.sourceforge.net
>     <mailto:Nagios-users at lists.sourceforge.net>
>     > <mailto:Nagios-users at lists.sourceforge.net
>     <mailto: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
>     >
>
>     > -- madunix
>
>     -----BEGIN PGP SIGNATURE-----
>     Version: GnuPG v1.4.7 (MingW32)
>
>     iD8DBQFHe4uudS4H/t4eKFARAs2AAJ96P7cFl6FbjfyyziCteVC1f6jjzQCeOUsD
>     lPm5a/zsumegOtL//METaRI=
>     =5Tau
>     -----END PGP SIGNATURE-----
>
>
>
>
> -- 
> madunix
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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