Issue with Check_NRPE Services

[REFan]

Having an issue with adjusting thresholds for linux services. We just want to adjust the warning and critical values for check_nrpe's check_procs service. I changed the values in the CCM but its not changing the status. If I run the "Run Check Command" it is correct but the service is still reporting its an issue.

Seems to be an issues for all the NRPE services we are running so not sure if making changes to these are different from the Standard Windows services compared to Linux.

[scottwilkerson]

Can you please post the configurations you have, both before and after?

[REFan]

I looked at a config from earlier today but they the same. Both reflect the original values that I am trying to change but if i go to the service in the CCM I see that the ARG2 values are set to -a '-w 400 -c 450'

define service {
host_name hibtv-lnx1.hi.corp
service_description Total Processes
use xiwizard_nrpe_service
check_command check_nrpe!check_procs!-a '-w 150 -c 250'!!!!!!
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
notifications_enabled 0
contacts hesijo10
_xiwizard linux-server
register 1
}





define service {
host_name hibtv-lnx1.hi.corp
service_description Total Processes
use xiwizard_nrpe_service
check_command check_nrpe!check_procs!-a '-w 150 -c 250'!!!!!!
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
notifications_enabled 0
contacts hesijo10
_xiwizard linux-server
register 1
}

[scottwilkerson]

did you apply configuration?

[REFan]

Yes with multiple changes and adjustments. I just did this one more time and looked at the config snapshot and I see it is still 150 and 250. These couple servers have been added through the regular Linux wizard.

[scottwilkerson]

In the CCM if you click the disk icon next to one of these services you changed does the config show -w 400 -c 450

[REFan]

Ah Ive never clicked that before. I do see that it is set to 400 and 450 but the service is still in critical with 373 process

define service {
host_name hibtv-lnx1.hi.corp
service_description Total Processes
use generic-service
check_command check_nrpe!check_procs!-a '-w 400 -c 450'!!!!!!
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
notifications_enabled 1
contacts _goleke10
_xiwizard linux-server
register 1
}

[scottwilkerson]

It is possible the config file is stuck and not written on apply config.

Lets do the following
Open CCM
Tools > Write Config Files
Click the Delete button
It will say "Successfully deleted all Host / Service Config Files"
Click the Write Button
It will show an output of all the files it creates, in large deployments this step may take a long time .
Click the Verify button

If all is OK, Apply Configuration

[REFan]

No difference after that. If i click the service, go to reconfigure this service, make changes to the critical and warning values and click update, then do those steps again to check the values they are not changed.
I originally thought that was only happening for Linux items but i just tested on a windows server thats running the NSClient and it does the same thing. If you look at the service in the CCM it is correct but the monitor does not use the changed values to determine critical or warning.

This week other team members upgraded our Nagios server from Cent OS 6 to Cent OS 7. I am seeing a few strange things after this upgrade but this is probably the biggest issue.
Running Nagios XI 5.4.12

[scottwilkerson]

Can you PM me a system profile
Admin -> System Profile

I'll have a look and maybe something will pop out at me