Nagios Support Forum

Understand. No need. I just hoped there was something I didn't know. You can close the ticket.

I would say the only practical way to deal with this for me is to force all those to be warnings. Since I'm only firing when services are not running that are supposed to be, I don't want to cherry pick. I'd just like this to be WARNING instead of CRITICAL.

Sorry.

CheckServiceState

No values.

Installed Version: 2014R2.7
Centos 6.7

Good morning,

Can I change a check_nrpe check from Critical to Warning?

Regards

Yes

I stand corrected. I missed the first $ sign. Don't think I've ever escaped anything with a $ sign before and I used to be pretty decent with regex.

Thanks for you help.

Thanks tgriep but it didn't have any effect. No error, but the service is not excluded.

Sorry for delay. Busy this time of year.

Please find the attached file.

Thanks but it didn't work. It works on the command line but not in the test or where it matters. In the test it gives me this. OUTPUT: Could not construct return packet in NRPE handler check client side (nsclient.log) logs... It has no effect in the nagios output. The service still shows up. So both...

Sorry about the delay. I've been tied up. While I haven't SPECIFICALLY looked at the core interface, I'm using clients on my phone and pc that look at core and they had the same issue when I applied the check the last couple of times.