Hello,
It appears whenever I apply a Nagios XI update the check_xi_service_tcp command changes to:
"$USER1$/check_tcp -H $HOSTADDRESS$ $ARG1$"
This causes all of my check tcp port services to report Critical.
Adding the -p (For the port number) back the command resolves the issue. "$USER1$/check_tcp -H $HOSTADDRESS$ -p $ARG1$"
This happened when I installed the 2011R1.9 and 2011R2.0 updates. Just thought I would make you aware.
Regards
Nagios Check TCP
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios Check TCP
Thanks, we will will look into the upgrade process.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios Check TCP
After looking at the wizard, the check_xi_service_tcp command is supposed to be
"$USER1$/check_tcp -H $HOSTADDRESS$ $ARG1$"
and the wizard places the -p flag in $ARG1$ before the port.
This would be expected behavior, if you modified the command, you really should create a new command and use that, all of the XI commands are reset on upgrade so the wizards work.
"$USER1$/check_tcp -H $HOSTADDRESS$ $ARG1$"
and the wizard places the -p flag in $ARG1$ before the port.
This would be expected behavior, if you modified the command, you really should create a new command and use that, all of the XI commands are reset on upgrade so the wizards work.