R: timing of passive check results

[Marco Borsani]

I have 2 remote servers, both with same configuration.

The remote server that does not send information (or could be the main that
does not process them?!!?) have about 50 services ... only 15 of them
(always the same, from same hosts) have this problem.

I use obsess method to send info from remote to main server and set an
higher timeout (ocsp_timeout=20)

Marco

-----Messaggio originale-----
Da: Andreas Ericsson [mailto:ae at op5.se] 
Inviato: mercoledì 14 dicembre 2011 11:12
A: Nagios Users List
Cc: Marco Borsani
Oggetto: Re: [Nagios-users] timing of passive check results

On 12/14/2011 10:09 AM, Marco Borsani wrote:
> Hi all
> 
> I have more than 400 passive service checks in the main Nagios server, 
> but
> 15 of them are updated only 1 time a day (always at the same time, 
> 5:36 in the morning).
> 
> In the remote servers the checks run every 5 minutes and in the main 
> server all the passive services have same configuration.
> 

I'm guessing you have configured passive checks in more than one place on
the remote servers and just overlooked the fact. Things like this doesn't
happen by itself.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and terror,
I think we should give some serious thought to declaring war on peace.


------------------------------------------------------------------------------
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits? 
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/
_______________________________________________
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