Miroslaw Horbal wrote:
>
> In this version, submit_check_result will run send_nsca in the
> background (similar to forking the process). This time
> submit_check_result will only execute send_nsca, but it will not wait
> for send_nsca to finish running. This effectivly reduces the runtime
> of subm
Have you tried modifying the OCSP command? More specifically, have you
optimized the command to have the lowest possible runtime. I noticed
that only one instance of the OCSP command is executed at a time and
this can lead to very high latencies when a large number of checks are
queued for submissi
On 5/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] schrieb am 17.05.2006 20:09:16:
To me this is obviously a performance issue related to hardware.
Your machines have way too few RAM. It is totally not possible to
run 1800 checks on a 512MB machine in a timely manner.
On 5/18/06, Tedman Eng <[EMAIL PROTECTED]> wrote:
Try tuning the intercheck_delay_method setting. This setting determines the
initial spreading out of the checks in the queue during a fresh start.
Nagios tries to do a good job of this, but if you have some checks spaced at
vastly different inte
2006 5:26 PM
> To: nagios-users@lists.sourceforge.net
> Subject: Re: [Nagios-users] How to reduce a very high latency number
>
>
> > I've noticed we get this problem when there are more than
> one or two hosts
> > down. Because Nagios (we use 1.2) does host checks f
I've noticed we get this problem when there are more than one or two hosts
down. Because Nagios (we use 1.2) does host checks first, and sequentially,
a host check timing out can hold up everything else (we have >3000 checks to
run every 5 minutes).
I have no hosts down 95% of the time, includ
On Mer 17 mai 2006 20:09, Trask wrote:
> I am still butting up against very high latency issues with my Nagios
> setup. I feel like I must be missing something obvious because it
> doesn't seem like I have so many services that the servers cannot keep
> up.
[snip]
How is set service_reaper_freq
My first reaction is to question why some checks are taking >15 minutes
to complete (check execution time) and why you are allowing them to go
that long. I only allow a maximum of 60 seconds for any service check to
execute --
(from nagios.cfg)
service_check_timeout=60
host_check_timeout=30
event
[Trask wrote]
> I am still butting up against very high latency issues with my Nagios
> setup. I feel like I must be missing something obvious because it
> doesn't seem like I have so many services that the servers cannot keep up.
I've noticed we get this problem when there are more than one or
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Trask
> Sent: Wednesday, May 17, 2006 1:09 PM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] How to reduce a very high latency number
>
> I am still butting up agains
Ok, I've decided to not wait before addressing the "tuning" doc
(http://nagios.sourceforge.net/docs/2_0/tuning.html). Also, thanks
for the link Jim, there is some good information there.
(Doc) 1. Use aggregated status updates.
(me) Doing this.
(Doc) 2. Use a ramdisk for holding status data.
Ok, that is all I can think of off the top of my head. I have
reviewed the performance tuning tuning doc (from here:
http://nagios.sourceforge.net/docs/2_0/tuning.html), but I am open to
trying things again / in a different way. I can list off what I've
done in response to that doc on a point-by
12 matches
Mail list logo
