next »

[familyguy]

What's the "correct" method of making apinger more tolerant of connections that show occasional bouts of latency?

I'm getting lots of spurious:

apinger: ALARM: an IP address (an IP address) *** delay ***

syslog messages for a link that (according to nagios) the routers on both ends think is just fine.

Thanks,

[familyguy]

Nobody?

[ermal]

Apinger does the checking far more often than nagios does.

[familyguy]

Apinger does the checking far more often than nagios does.

Great.  So how can I influence how tolerant apinger is of occasional (non-fatal) latency?

[databeestje]

You might need to read the thread in the 2.0 forum, the sticky apinger thread there explains all.

[familyguy]

You might need to read the thread in the 2.0 forum, the sticky apinger thread there explains all.

Perhaps it is right under my nose, but I looked through all the stickies and did a search and  I didn't see a thread about tuning apinger.  I'd appreciate it if you could point me at the thread you're referring to.

Best,

[familyguy]

Pretty please with sugar on top???   

[databeestje]

I thought it was, or it isn't.

Anyhoo, unless it's a critical event and not a warning you can safely ignore the message.

We log warnings, but only act on critical events. Changing the defaults on 1.2.3 involves touching code.