I am using Nagios 3.0b1. My Nagios server is it's own box that I have other
monitoring software on. I have 3 production coldfusion servers that I would
like to monitor through my nagios server.
_____
From: Valdinger, Stephen (DOV, MSX) [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 15, 2007 10:05 AM
To: Jeff Perri; [email protected]
Subject: RE: [Nagios-users] How to monitor coldfusion through nagios
Why not use the check_procs that is available in the standard plugins? You
can use the -p switch to supply the PID of the process you are wanting to
monitor. I don't have coldfusion installed, but I think a ps -ef | grep
coldfusion would help you find that number if you are unsure of it.
What version on Nagios are usings? The plugins? Is this process on the same
machine as the Nagios process, or is it on a remote machine?
Please provide a little more information to the list so that we may better
assist you.
Stephen
From: Jeff Perri [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 15, 2007 9:57 AM
To: [email protected]
Subject: [Nagios-users] How to monitor coldfusion through nagios
Hi,
I have been searching around looking for a plugin that allows me to monitor
my coldfusion process on a Linux machine but I have yet to find one. Has
anyone implemented this type of plugin yet or does anyone know how I would
monitor this process via Nagios?
Thanks
Jeff Perri
Network Administrator
Ontario WorkInfoNet
Sault Ste. Marie, Ontario
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
[email protected]
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
