I fixed the problem!
It was an issue with our Check Result Reaper Frequency and Maximum Check
Result Reaper Time, adjusting these fixed the issue.
Thanks for the pointers!
Doug Eubanks
ad...@dougware.net
K1DUG
(919) 201-8750
On Fri, Dec 7, 2012 at 2:56 AM, Claudio Kuenzler
wrote:
> On Fri,
Hello Robert,
This is my command:
# 'check_mssql_health CPU Usage' command definition
define command{
command_namecheck_sql_cpu
command_line$USER1$/check_mssql_health -server $HOSTADDRESS$ -username
$ARG1$ -password $ARG2$ -mode $ARG3$
}
This is my service check for said se
Re-tested after changing the max file size of the debug file.
This one should contain everything from the moment I started Nagios to the
moment I stopped it during testing (approx. 10 minutes)
http://dl.dropbox.com/u/895609/nagios.debug
Thankyou
-Original Message-
From: FTL Nagios [mail
Hi,
Apologies for the delay, been very busy with other things.
Right I have put Nagios into Debug this morning and rerun the tests.
I let it get a couple of successful pings to the server then pulled the
network cable from it.
Behaviour is completely different this morning
The host check i
Andrew Daugherity writes:
> I'm troubleshooting an issue where one server is occasionally not responding
> (I think it's a firewall or snmpd issue, not this plugin), and I noticed that
> changing the timeout option to check_openmanage did not affect how long it
> took before receiving the
>
