Hi,
check the i/o on disk. If you graph lots of checks or simply write the
status.dat on slow disk, everything gets slow.
Io you find the disk being too taxed, try moving logs and status.dat on ramdisk.
Giorgio
--
L
Simon, have you tried enabling the use_large_installation_tweaks=1 option
in nagios.cfg?
Enabling that option helps me eliminate the check latency but increases the
load on cpu significantly.
You may want to give that a try.
Jake
On Wed, May 23, 2012 at 2:52 AM, Simone Felici wrote:
> So, cpul
So, cpuload is stable around 5.00 - 5.50. IO wait is difficult to identify.
Using top I can read an average of 0% with some peaks up to 4%. Using iotop the
process kjournald is
jumping on first position often with peaks to 10-20%, back to 0 immediatly.
Second place for nagios process. But the 1se
Il 22/05/2012 16:25, Assaf Flatto ha scritto:
> One thing I found to help with performance with NDO was to make sure the DB
> is trimmed on a regular
> basis .
> tables timedevents, services , logentries and other ones grow very fast to
> large size and nagios is
> having trouble writing to the
What kind of information do you have about average CPU load or I\O wait
time? Whether Nagios is using ndoutils or not there will be a hardware
limit as to how many disk writes it can handle in a given period of
time. Even though you're only running a few active checks, it could be
a symptom t
On 22/05/12 13:55, Simone Felici wrote:
> Il 22/05/2012 13:55, C. Bensend ha scritto:
>
>> I bet you're using NDOUtils. I wouldn't recommend that. I couldn't
>> keep a Nagios server with under 6000 services limping along when
>> NDOUtils was running. Eventually, the check latencies would go
>> t
Il 22/05/2012 13:55, C. Bensend ha scritto:
> I bet you're using NDOUtils. I wouldn't recommend that. I couldn't
> keep a Nagios server with under 6000 services limping along when
> NDOUtils was running. Eventually, the check latencies would go
> through the roof and the entire server would get
> I've some broker modules to handle sql logging and distributed setup.
I bet you're using NDOUtils. I wouldn't recommend that. I couldn't
keep a Nagios server with under 6000 services limping along when
NDOUtils was running. Eventually, the check latencies would go
through the roof and the en
This could be the case. Is there a way I can log and explicit find out some
traces that could point
me to the real causes?
I'm collecting on MySQL everything is generated by nagios itself: status and
performance data, which
are a lot of informations: 7GB of runtime statistics.
Il 22/05/2012 1
NDO and a large DB cause an issue to the nagios core that is causing
high latency and can bring nagios to halt.
If you are also running a performance gathering solution it can
contribute to the hight latency .
On 22/05/12 08:46, Simone Felici wrote:
> Hello!
>
> Yes, it's a common problem, bu
Hello.
My case was Nagios latency was caused by java.
Little tuning with java helped me out.
# java and nagios had absolutely no relations.
Thanks,
Yu
>Hello!
>
>Yes, it's a common problem, but cannot figure out how to debug it.
>I've a distributed setup with a master server collecting >9.000 p
Hello!
Yes, it's a common problem, but cannot figure out how to debug it.
I've a distributed setup with a master server collecting >9.000 passive
services sent from other
servers, all with active latencies near 0. The master server checks *only*
itself as active
services, ~40 services, most of
Hi all:
Dell PE2950, 16GB ram, plenty of disk space, etc
Just upgraded to Nagios 3.3.1 from Nagios 3.2.3
MySQL 5.0.77
NDO2DB 1.4b9
RRDTool 1.4.5
NRPE 2.8.1
Been using nagios for a while (nagios 2.x) and I have been upgrading,
the latest upgrade from 3.2.3. Every other upgrade has gone
13 matches
Mail list logo
