check_http and hard coded port in commands.cfg
Posted: Fri Apr 24, 2015 8:14 am
Newbe warning: Just given ownership of Nagios and have no exposure, so I seek advice. (Core and after installed XI on CentOS 6.4 64 bit).
Someone before me have hard coded a port - that is now a problem.
I am only using /usr/local/nagios/etc/static (and in commands.cfg I got:
command_name check_endpoint
command_line $USER1$/check_http -H $ARG1$ -u $ARG2$ -p 443 –S
So, the port 443 is hardcoded and one of my end_point checks are using port 8888.
What is the quickets/eaasiest way for a work around? (I am going to have to clean upp all of Nagios laters as it is a right mess.)
Do I just create a separate .cfg file for this customer? Customer now live in /usr/local/nagios/etc/static/objects/customers.cfg Remove the customer from there
and in this specific customer's .cfg file call with:
command_line $USER1$/check_http -H $ARG1$ -u $ARG2$ -p $ARG3$ –S
As I am totally new to Nagios I am only guessing here. I don't know where the actual call is being made and what else to change. What else have I missed?
Cheers
/G
Someone before me have hard coded a port - that is now a problem.
I am only using /usr/local/nagios/etc/static (and in commands.cfg I got:
command_name check_endpoint
command_line $USER1$/check_http -H $ARG1$ -u $ARG2$ -p 443 –S
So, the port 443 is hardcoded and one of my end_point checks are using port 8888.
What is the quickets/eaasiest way for a work around? (I am going to have to clean upp all of Nagios laters as it is a right mess.)
Do I just create a separate .cfg file for this customer? Customer now live in /usr/local/nagios/etc/static/objects/customers.cfg Remove the customer from there
and in this specific customer's .cfg file call with:
command_line $USER1$/check_http -H $ARG1$ -u $ARG2$ -p $ARG3$ –S
As I am totally new to Nagios I am only guessing here. I don't know where the actual call is being made and what else to change. What else have I missed?
Cheers
/G