Hi there --
I am running Nagios 3.1.2 with OpMon, formally NSClient, agent 2.0 installed on
a Windows 2008 R2 64-bit system. I have several
counters that are being monitored on the client including CPU Load, Disk Usage,
Memory Usage, Server Uptime, and Paging File Usage.
All counters except Paging File Usage appear to be running without issue.
The error message that I am seeing with Paging File Usage is the following:
NSClient - ERROR INVALID COUNTER - PagingFile(_Total)% Usage - ERROR CODE:
0xC0000BB8 -
I have a Windows 2003 R2 64-bit server that is being monitored with the same
counters, and the Paging File Usage counter does not
return an error. The syntax for the command in question, taken from the
commands.cfg file, is shown below:
# 'check_nt_pagingfile' command
define command{
command_name check_nt_pagingfile
command_line $USER1$/check_nt -H $HOSTADDRESS$ -p 5667 -v COUNTER -l
"\\PagingFile(_Total)\\% Usage","Paging Fileusage is %.2f%%" -w $ARG1$ -c $ARG2$
}
Does anyone know what change(s) are needed to the above command, assuming it can
still be used, in order for it to accurately
keep track of the paging file in the Windows 2008 server?
Thanks.
The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null