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
If you go to "Acknowledge" a host or service in a problem state, there
is a checkbox for whether or not to send a notification. If you want
the notification use the "Acknowle this service problem" link instead of
the "Add Comment" link.
On 5/21/2012 5:41 PM, Ajay Jethani wrote:
I'd like nagi
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
Dear fellow Nagios users,
We have a bunch of servers on which we have shared filesystems. The
filesystem actually resides on the SAN storage and are connected to
physical servers. Let's say /home is shared among server1 and server2.
When /home breaches the WARNING or CRITICAL threshold it raises
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
10 matches
Mail list logo
