Distributed Monitoring Web Interface Issue

[Marco Supino]

Hi,

 

You are right, I also modified a source file, allowing freshness to run
even in check_period=none, this is the patch, if a service has check
freshness, it will run it.

 

Marco.

 

 

nagios at nms:~$ diff -Naur /tmp/new/nagios-2.8/base/checks.c
/tmp/nagios-2.8/base/checks.c

--- /tmp/new/nagios-2.8/base/checks.c   2007-03-01 14:15:10.000000000
-0500

+++ /tmp/nagios-2.8/base/checks.c       2007-03-13 04:10:46.000000000
-0400

@@ -1732,8 +1732,8 @@

                if(temp_service->is_being_freshened==TRUE)

                        continue;

 

-               /* see if the time is right... */

-
if(check_time_against_period(current_time,temp_service->check_period)==E
RROR)

+               /* see if the time is right... but we're using
auto-freshness threshold */

+
if(check_time_against_period(current_time,temp_service->check_period)==E
RROR && temp_service->check_freshness==FALSE)

                        continue;

 

                /* EXCEPTION */

@@ -1741,6 +1741,7 @@

                if(temp_service->check_interval==0 &&
temp_service->freshness_threshold==0)

                        continue;

 

+

 #ifdef TEST_FRESHNESS

                printf("CHECKFRESHNESS 3\n");

 #endif

 

________________________________

From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Jeff
Shumard - DefenseWeb Technologies
Sent: Wednesday, May 09, 2007 20:58
To: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Distributed Monitoring Web Interface Issue

 

Marco,

 

I have the same issue with all my services showing up as disabled
because I have active checks turned off on my Centralized Nagios
Interface.  I and running Nagios 2.9 and I configured what you said but
that didn't fix the problem it just caused a couple of others.  Here is
what I did bellow.

 

1)       I didn't configure the service to have active_checks on and had
no check_period configured.  This did resolve the issue of the service
saying disabled because the active check was turned on.  This caused
another problem.  The active checks were being done after 30 seconds way
before my freshness_threshold of 600 seconds and my
normal_check_interval of 3 minutes.  It shouldn't have checked it at
all.

 

2)       I tried it another way of creating a check_period called none
which had not times configured to check.  I made the service use this as
its check_period.  When I did this it then never ran an active check
even though I had a freshness_threshold configured.

 

Is there something I did wrong, or are you running an older version of
Nagios then 2.9?  If anyone else has found a resolution to this problem
I would appreciate your comments.

 

Thank you,

Jeff

________________________________

From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Marco
Supino
Sent: Tuesday, May 08, 2007 10:43 PM
To: Simon Marcil; nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Distributed Monitoring Web Interface Issue

 

Hi,

 

I have the same scenario, and what I did was to enable active checks on
all services, but put check_period to none, so a check is never
executed, except if freshness checking runs it.

 

Marco.

 

 

________________________________

From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Simon
Marcil
Sent: Wednesday, May 09, 2007 02:59
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Distributed Monitoring Web Interface Issue

 

I have a distributed monitoring setup. I have several servers reporting
back to a central server. The central server also does a couple checks
but most of it's hosts and services are disabled (because it receives
the info from other servers).

 

The problem I have is with the web interface. In the Tactical Overview
all the problems reported from distributed servers show up as
"disabled". This means that we can't have a correct listing of Unhandled
Problems. For example, Let's say I have 3 hosts down coming from a
distributed server with 1 that has been acknowledged. I will have the
following:

 

3 Down

1 Acknowledged

3 Disabled 

 

In this example, is there a way to only list the host which are down and
not acknowledged???

 

If this wasn't clear let me know and I will clearify.

 

Simon

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070509/2987f9fa/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
-------------- next part --------------
_______________________________________________
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