After some more trial and error, I got the command check fixed but there is still an issue.
The command I am sending is: r...@van-nagios:/usr/local/nagios/libexec# ./check_nt -H van-mail01 -s xr1p71c -p 12779 -v COUNTER -l "MSExchangeIS Mailbox(_Total)\\Messages Delivered/min" -w 25 -c 120 The output is: 0 When I check nsclient.log; here is what I have: 2009-05-06 11:09:18: debug:.\NSClientListener.cpp:146: Data: xr1p71c&8&“MSExchangeISConnection 2009-05-06 11:09:18: debug:.\NSClientListener.cpp:171: Data: “MSExchangeISConnection 2009-05-06 11:09:18: debug:.\NSClient++.cpp:910: Injecting: checkCounter: Counter=“MSExchangeISConnection, nsclient 2009-05-06 11:09:18: error:.\CheckSystem.cpp:1019: ERROR: Counter not found: “MSExchangeISConnection: The counter path string could not be parsed. 2009-05-06 11:09:18: error:.\CheckSystem.cpp:1021: ERROR: Counter not found: “MSExchangeISConnection: The counter path string could not be parsed. 2009-05-06 11:09:18: error:.\CheckSystem.cpp:1050: ERROR: “MSExchangeISConnection: PdhAddCounter failed: -1073738816: Unable to parse the counter path. Check the format and syntax of the specified path. (“MSExchangeISConnection|“MSExchangeISConnection) Where is "“" coming from?? -----Original Message----- From: Mirza Dedic [mailto:mi...@oppy.com] Sent: May/06/2009 10:32 AM To: 'nagios-users@lists.sourceforge.net' Subject: [Nagios-users] NSclient++ Performance Counters Help ?? Hello, I am trying to use NSClient++ to monitor performance counters; previously I only used it to check disk space etc, but I am trying to make sure of the "-v COUNTER -l" switch more now as it is very powerful. In my config I have: define command{ command_name check_nt_exchange_messages_delivered_per_min command_line $USER1$/check_nt -H $HOSTADDRESS$ -s password -p 12489 -v COUNTER -l "MSExchangeIS Mailbox(_Total)\\Messages Delivered/min" -w 25 -c 120 } However, when I try to test this from my box with: ./check_nt -H van-mail01 -s xr1p71c -p 12779 -v COUNTER -l "MSExchangeIS Mailbox(_Total)\\Messages Delivered/min" -w 25 -c 120 I get: bash: syntax error near unexpected token `(' Also, on Nagios it reports as "null"; which I would assume is because of the above syntax issue. How can I fix this? The source I got my counter from is: http://www.hackmyidea.com/wordpress/2007/11/14/misc-windows-checks-for-nagios/ Also, I noticed in my NSClient++ installation in the windows box (Exchange 2005/Win2003) there is a counters.defs file, should I be making use of that and entering the counters in there as opposed to calling them from commands.cfg ? If so, how could I use the ./check_nt to call a performance counter defined in counters.defs ? (assuming this is what its for?). Thanks. ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ 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 ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ 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