On Mon, Jan 10, 2011 at 8:33 AM, Rajesh Kumar <ras.kuma...@gmail.com> wrote:
> Hi All > > > > I have installed Nagios Core in my CentOS but not able to configure > port based check_http. We are using several port in apache-tomcat in remote > server. We can able to configure default port 80. I have to need to > configure server port of 8082, 8084 … could you assist me port based > configure on nagios. This is my cfg file of check_http. > > > > define host{ > > use linux-server > > host_name USSERVER > > alias USSERVER > > address saas-testing.com > > } > > define service{ > > use generic-service > > host_name USSERVER > > service_description HTTP > > check_command check_http > > check_interval 3 > > check_period 24x7 > > retry_interval 2 > > max_check_attempts 2 > > notification_interval 5 > > notification_period workhours > > notification_options w,c,u,r > > notifications_enabled 1 > } > > Regards > > B.Rajeshkumar > Your check command definition (which you didn't attach) should look something like: define command{ command_name check_http command_line $USER1$/check_http -H $HOSTADDRESS$ -p $ARG1$ } Then the check_command argument in your service definition, if you were checking port 80, would look like: check_command check_http!80 If you want to check other ports, then you'll have to create a different service for each port you want to check. -- James Moseley
------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ 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