Upgraded NetSaint to Nagios 1.1 - trouble in paradise!

[Jan Scholten]

For the Host try entering check_host_alive and in the checkcommands.cfg  
define check_host_alive as:

define command{
         command_name    check-host-alive
         command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80%  
-c 5000.0,100% -p 1
         }

This is how it works with 1.2 (why did you upgrade to an old version?)


Jan


> I upgraded to Nagios 1.1 and used the convertcfg script to conert my  
> original hosts.cfg file.
> Item 1. Now my check_ping isn't working.
> How can I manually confirm the check_ping output?
> Item 2. Status of the hosts stays as unknown
> I tried adding a check_command check_ping and I get a host down when it  
> is up and
> an error - check_ping: %s: Warning threshold must be integer or  
> percentage.
> I have the check_ping defined as
> check_ping!100.0,20%!500.0,60% in my services.cfg file, if I try adding  
> the same thing in the hosts.cfg file I get errors not allowing it.
> If I remove the check_command from my host file I thought the host was  
> suppose to show as up all the time and it doesn't, it still shows as  
> unknown status and red as if it is down. I start and stop nagios between  
> changes and even rebooted linux with no luck.
> Any ideas?
>
>
> The Best Computer Upgrades - Check it out!
> 		
> ---------------------------------
> Do you Yahoo!?
> vote.yahoo.com - Register online to vote today!



-- 
Jan Scholten
Research and Development Intern
Iconz.co.nz


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
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