Hi all;
I'm a system admin who got this machine runs with nagios 2.x and will
migrating it to 3.x soon.
Anyway I love to do deep monitoring on existing exchange server.
Referring to guide from nagiosexchange,
http://exchange.nagios.org/directory/Plugins/Email-and-Groupware/Microso
ft-Exchange/Che
There is a debug level you can set in nagios.cfg that will show you
all commands being executed - an easier way would be to make a shell
wrapper for check_int that logs all args and then execs them with the
real check_int. Something like
1. Copy check_int to check_int.bin
2. Make check_int a sh
I have a couple R610’s
Some run omreport chassis pwrmonitoring & return output
I also have 1 that returns:
# omreport chassis pwrmonitoring
Power Consumption Information
Error : Current probes not found
Does this mean that this module just isn’t installed or ???
At this point, do I just alter th
I am out of the office until 24/02/2011.
I am currently out of the office, and your email has not been forwarded.
Note: This is an automated response to your message "Re: [Nagios-users]
NAGIOS does not register "Critical" | "Warning" status." sent on 2/23/2011
1:17:41 AM.
This is the onl
On Mon, 21 Feb 2011 20:23:54 -0500, Allan Clark
wrote:
> Can you confirm that "%%" is needed for a single "%" token? I don't
> remember that being needed, but I don't use "%" in my commands. I
> could see "$" needing doubling up due to token replacement.
Apparently check_nt will returns same co
Cheers for the reply guys.
Sadly, as I'm looking after only one of a few sites that each has its own
Nagios server and all the windows servers have Nsclient 3.3 installed. I can't
upgrade the version to support the newer commands as EVERY windows server in
the business would then need upgrading
On 02/22/2011 03:13 AM, Yueh-Hung Liu wrote:
> because at any moment in physical, not all checks will be performed,
> therefore Nagios only knows the "previous" average latency and the
> latency of services which have just finished.
> Nagios won't keep the latency of checks in somewhere so it has t
Thank you for the reply.
This logic seems to be deep ...
I will take time to digest this theory.
Thanks!
Yu
Yueh-Hung Liu さんは書きました:
>because at any moment in physical, not all checks will be performed,
>therefore Nagios only knows the "previous" average latency and the
>latency of services which
