FW: Check Exchange Queues

[Ray La Peyre]

How do you start perfmon? This is a live server so exchange will be
started constantly. I know that you can just go start run perfmon to
bring it up but I dont know how that can help me get the nagios
monitoring to work

________________________________

From: Steve Shipway [mailto:s.shipway at auckland.ac.nz] 
Sent: Monday, 3 July 2006 7:58 AM
To: Ray La Peyre; nagios-users at lists.sourceforge.net
Subject: RE: [Nagios-users] Check Exchange Queues


Sometimes, windows servers have problems with service order.  Make sure
you have started exchanege before you start perfmon, so that perfmon can
verify the counters from exchange  Or is it the other way around?  We
have a problem with SQLServer where if you restart the (SQL) service all
the perf counters disappear.  This is a microsoft... 'feature'...
 
S teve 


	Is there any configuration I need to make on the Exchange
Server? (other than installing NSClient)
	 
	I have setup this up on the nagios box but I am just getting:
	 
	0 messages queued 
	Performance Data: '%.0f messages
queued'=0.000000%;10.000000;15.000000 
	
	No matter how many messages are in the queue
	 
	This is the check command that I am using:
	 
	check_command          nt_exch_outq!10!15
	
	 
	Thanks


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060703/0ecf74fb/attachment.html>
-------------- next part --------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at 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