Nagios

On Nov 30, 2009, at 11:16 AM, john wrote:

> Here's the host and service that isn't alerting (ip removed):
> 
> define host{
>     host_name                           moocow
>     check_interval                      1800
>     notification_interval               1800

Unless you've changed interval_length, these are in minutes. 1800m == 30 hours.

>     normal_check_interval               300

5 hours

>     retry_check_interval                120

2 hours.

>     notification_interval               7200

5 days.


--
Marc

If anyone figures this out it would be greatly appreciated. I posted about
the same thing a few weeks back. I had services defined with
"max_check_attempts" set to 3 and wasn't getting alerted because it would
get stuck on the first or second attempt. After digging through my logs I
saw that when this was happening, the service would go critical but the next
check would never occur. There may be some strange bug in the code that
schedules retries. I'm not sure, but I added a cleanup script that shuts
down nagios, removes all temporary files and restarts which seems to fix the
problem for a short while.



On Mon, Nov 30, 2009 at 12:16 PM, john <lists@...> wrote:

> I've moved my config from an old nagios2 installation to nagios 3.0.6
> (debian's version) and when performing checks, it only seems to do one
> service check attempt so never seems to alert.
>
> I've got various things in an unknown and critical state but they are all
> listed as Attempt 1 of 3 even if I force an active check to occur. My
> intervals for checking haven't changed since nagios2
>
> Here's the host and service that isn't alerting (ip removed):
>
> define host{
>     host_name                           moocow
>     alias                               moocow
>     address                             x.x.x.x
>     parents                             switch1
>     hostgroups                          servers
>     check_command                       check-host-alive
>     max_check_attempts                  3
>     check_period                        24x7
>     check_interval                      1800
>     retain_nonstatus_information        1
>     contact_groups                      notify.john
>     notification_interval               1800
>     notification_period                 24x7
>     notification_options                d,u,r
> }
>
>
> # PING
>
> define service{
>     host_name                           moocow
>     service_description                 PING
>     servicegroups                       servers
>     max_check_attempts                  3
>     normal_check_interval               300
>     retry_check_interval                120
>     check_period                        24x7
>     contact_groups                      notify.john
>     notification_interval               7200
>     notification_period                 24x7
>     notification_options                w,u,c,r
>     check_command                       check_ping!75.0,20%!150.0,60%
> }
>
> Can anyone suggest why this wouldn't alert me?
>
> The config test only throws some warnings about "notification interval
> less than its check interval" but not for any services that are having
> this problem
>
> Cheers,
>
> john
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Nagios-users mailing list
> Nagios-users@...
> 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
>

On Mon, 30 Nov 2009, john wrote:

> I've moved my config from an old nagios2 installation to nagios 3.0.6
> (debian's version) and when performing checks, it only seems to do one
> service check attempt so never seems to alert.

Well, in true, spending ages looking for a problem, and then you post to a 
mailing-list and then you find the solution, style, I've found the 
problem:

normal_check_interval and retry_check_interval were renamed to 
check_interval and retry_interval respectively. Now to go and update all 
my config files :/

On Mon, 30 Nov 2009, Marc Powell wrote:

> Unless you've changed interval_length, these are in minutes. 1800m == 30
> hour

Yes, interval_length = 1, so in seconds. Sorry for bothering you!

Cheers,

john

On Nov 30, 2009, at 12:05 PM, john wrote:

> normal_check_interval and retry_check_interval were renamed to 
> check_interval and retry_interval respectively. Now to go and update all 
> my config files :/

They're interchangeable at this point. Either will produce the exact same results.

        else if(!strcmp(variable,"check_interval") || !strcmp(variable,"normal_check_interval")){
            temp_host->check_interval=strtod(value,NULL);
            temp_host->have_check_interval=TRUE;
                }
        else if(!strcmp(variable,"retry_interval") || !strcmp(variable,"retry_check_interval")){
            temp_host->retry_interval=strtod(value,NULL);
            temp_host->have_retry_interval=TRUE;
                }

--
Marc

On Mon, 30 Nov 2009, Marc Powell wrote:

> On Nov 30, 2009, at 12:05 PM, john wrote:
>
>> normal_check_interval and retry_check_interval were renamed to
>> check_interval and retry_interval respectively. Now to go and update all
>> my config files :/
>
> They're interchangeable at this point. Either will produce the exact same results.
>
>        else if(!strcmp(variable,"check_interval") || !strcmp(variable,"normal_check_interval")){
>            temp_host->check_interval=strtod(value,NULL);
>            temp_host->have_check_interval=TRUE;
>                }
>        else if(!strcmp(variable,"retry_interval") || !strcmp(variable,"retry_check_interval")){
>            temp_host->retry_interval=strtod(value,NULL);
>            temp_host->have_retry_interval=TRUE;
>                }

You are right. I'm currently changing the config one line at a time to 
see what else I added fixed it so I can do all the other services!

john