[op5-users] Réf. : Re: Réf. : Re: Réf. : Re: Réf. : Re: Nagios start time delay with Merlin

Andreas Ericsson ae at op5.se
Thu Aug 27 10:44:54 CEST 2009


nicolas.raspail at bnpparibas.com wrote:
> op5-users-bounces at lists.op5.com wrote on 26/08/2009 14:53:40:
> 
>> Please test the beta5 of Merlin. The release-tag will be set where
>> the beta5 tag is now, unless our testing uncover some truly amazing
>> deficiency that we have so far been completely unable to spot (not
>> very likely). In all likelihood, 0.6.2 will therefore be the same
>> code as is in 0.6.2-beta5.
>>
>>> Right now, with NDO, my latencies seems to be stable with theses 
> values
>>> Service Check Execution Time:   0.04 / 30.02 / 0.372 sec
>>> Service Check Latency:  0.00 / 1299.86 / 46.321 sec
>>> Host Check Execution Time:      2.54 / 2.62 / 2.563 sec
>>> Host Check Latency:     0.00 / 3.45 / 1.179 sec
>>>
>> That's a fairly high service check latency though. Hopefully Merlin
>> will cope better than that.
> 
> Hello,
> 
> I have compiled and installed the new merlin 0.6.2-beta5 and it is
> running for 30 minutes now.
> 
> Nagios start checking hosts/services immediately,

That's a good thing. How does merlin affect latency now?

> but I see a strange
> behaviour of Merlin in the log file. Every 30/40s, the php importer is
> run. In Ninja, I can see the number of services changing from 0 to
> 14669, and the number of hosts from 0 to 1984. Does it mean that there
> is no history of past events in Merlin ?
> 

Correct. Ninja does not have yet have log-browsing capabilities, so
there is no state history in Ninja. Look to our reporting tool for
that.

> 
> It seems that merlind receive an update in the IPC socket and run the
> php importer soon ater. Is a normal behaviour in the beta5 version ?
> 

Yes it is. It happens when an event packet is, for some reason, dropped.
The module then backs off 15 seconds to let the daemon catch its breath
and then sends an event which triggers a re-import of the status.
This is a quirky workaround to a problem I'm debugging right now, which
is that the merlin daemon for some reason takes too long to read even
a single event (it seems to be 0.3 seconds + 0.1 second for each event
in addition to the first one, which is totally unacceptable).

-- 
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.


More information about the op5-users mailing list