Re: Nagios check latency

Muhamad Faiz <[email protected]> Wed, 21 Aug 2013 02:42:50 +0000
Newsgroups gmane.network.nagios.user
Message-ID <C322DBB5CEB78E47854B9568661B849C3449AFF7@xch-mbx07.camkmg-bangalore.com>
Hi Jim Avery,

I do a lot of configuration recently so starting and stopping was done quite a lot as well.

I guess two Nagios instance was running.

Regards,

Faiz

From: Jim Avery [mailto:[email protected]]
Sent: Tuesday, August 13, 2013 9:14 PM
To: nagios List
Subject: Re: [Nagios-users] Nagios check latency


On 13 Aug 2013 05:22, "Muhamad Faiz" <[email protected]<mailto:[email protected]>> wrote:
> My Nagios setup are having high service check latency.
>
>
>
> Check nagios latency result is 240 seconds!
...
> Any advice will be much appreciated.

If you haven't stopped / started the nagios daemon lately, then do that ("/etc/init.d/nagios stop"  then  "/etc/init.d/nagios start" ,  NOT "/etc/init.d/nagios reload").  I find that after a couple of weeks the service check latency starts creeping up, and stopping/starting the nagios daemon sorts it.

I hope that helps.

Jim
"CONFIDENTIALITY NOTICE: This message and any attachment are confidential and may also be privileged. If you are not the intended recipient of this e-mail you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you are not the intended recipient please telephone or e-mail the sender and delete this message and any attachment from your system."

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk

_______________________________________________
Nagios-users mailing list
[email protected]
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