Nagios Support Forum

This may or may not help but I have had to make a small update to my NSClient++ tests in the latest Nagios XI version.

I found that using the < and > characters were causing the GUI run test command to fail.

I replaced < with lt and replaced > with gt
<= is le
>= is ge

Once I did that the GUI test command started to succeed.

So,
"warning=load>=95%" "critical=load>=98%"
becomes
"warning=load ge 95%" "critical=load ge 98%"

Refer to https://docs.nsclient.org/checks/ anf look for "The operators available are:"

Also, if you copy the nagios/etc/services/[service.cfg] file to nagios/etc/import directory and make edits, then apply changes, it will make the update. This gives you a possible avenue for making global changes from the OS.

I hope this helps a bit.

Steve B

Thanks Steve - that is good to know, although we would have thousands of checks to change.

It would be good if the issue was resolved by the developers - now that you have identified a possible issue with symbol operators

I tried use ge instead of >= and it still did not work in CCM \ Run Check Command - still getting - Failed to validate filter see log for details

Command: check_nrpe

$ARG1$ - check_cpu

$ARG2$ - -a "warning=load ge 95%" "critical=load ge 98%" "time=1m" "time=5m" "time=15m" "filter=core = 'total'" "top-syntax=%(status): %(list)" "detail-syntax=%(time) load %(load)%"

Still getting from Core Configuration Manager \ Run Check Command - Failed to validate filter see log for details

/usr/local/nagios/libexec/check_nrpe -H 10.27.95.32 -t 30 -c check_cpu -a "warning=load ge 95%" "critical=load ge 98%" "time=1m" "time=5m" "time=15m" "filter=core = 'total'" "top-syntax=%(status): %(list)" "detail-syntax=%(time) load %(load)%"
Failed to validate filter see log for details|

Output displays fine in the Nagios XI GUI - just not in CCM

So same issue using >= or using ge

You mentioned ‘Optimizing the PHP settings. It's not uncommon to hit the limits when running large reports and making large changes ( max input variables)’.

Would you have a recommended value – I have searched the forum and most set max_input_vars to 50,000 or 100,000

If we bulk change thousands of services - what happens if it aborts during applying mass change?

Do you have to repair crashed tables or restore databases?

Hi Tony,

We recommend a setting of max_input_vars = 50000 in the KB article and that is usually sufficient. I would start on those values and go from there.

https://support.nagios.com/kb/article/n ... e-611.html

Normally, the GUI will hang or and PHP will timeout. I haven't seen that issue resulting in database corruption.

Benjamin

Hi,
version 5.7.5 is out which fixes the bug.
I am undecided to bring the working version 5.71 to 5.7.5.
Have you already done the test?

Regards,
-f

Hi Tony,

The 5.7.5 is a security release, you can view the full changelog here:

https://www.nagios.com/downloads/nagios-xi/change-log/

The next version of XI will be 5.8 (coming soon), and it will contain more features and bug fixes.

I upgraded my TEST build from XI ver 5.74 to 5.7.5. I also downloaded the 5.7.5 VM and tried it.

Unfortunately, version 5.7.5 does not fix the issue.

I am still getting from Core Configuration Manager \ Run Check Command - Failed to validate filter see log for details - when running my windows nsclient - check_nrpe commands with the above syntax.

Benjamin, did you check if we can install the Bulk Modification Tool version 2.3.0 from Nagios XI 5.7.4 in Nagios XI 5.6.14

Hi Tony,

I checked with an XI developer and it should work, but we haven't tested this out. Be sure to take a backup before making any changes.

Backing Up And Restoring Your Nagios XI System