Nagios Support Forum

We have recently did an upgrade from RHEL 7.4 to RHEL 7.9 and our nagiosXI 5.8.3 code is having issues. Specifically this:

In our command line when we check snmp storage it comes up like this:

XXXX:/usr/local/nagios/libexec]$ ./check_snmp_storage.pl -H XXX -C DCWest --v2c -m "^/$" -w 80 -c 95 -f
/: 81%used(38224MB/46973MB) (>80%) : WARNING | '/'=38224MB;37578;44624;0;46973

However when we view this through the website it comes up like this

[xxx~]$ /usr/local/nagios/libexec/check_snmp_storage_wizard.pl -H XXX -C DCWest --v2c -m "^/$" -w 80 -c 95 -f
Unknown storage : \^/$ : ERROR

What could cause a communication issue between the command line and website? Our original system was on RHEL 74 and then we upgraded to rhel 79. If you can provide any info that will help we will be glad to provide.

Hello @itunixops

Thanks for reaching out, want to find out if this was an in-place os upgrade? If so you will likely run into issues when doing an in-place upgrade. You would also likely need to do this after upgrading:

The error message; Unknown storage : \^/$ : ERROR is referencing disk path. You will want to try entering a known path and test the command. Examples:

Test drive C,F,G,H,I on Windows : -m ^[CFGHI]:
Test all mounts containing /var : -m /var
Test all mounts under /var : -m ^/var
Test only /var : -m /var -r
Test all swap spaces : -m ^Swap
Test all but swap spaces : -m ^Swap -e

Thanks,
Perry

We did and in place upgrade. The upgrade replaced rhel74 with 79. However we think we may have found the issue.
/usr/local/nagios/libexec/check_snmp_storage_wizard.pl -H XXX -C DCWest --v2c -m "^/$" -w 80 -c 95 -f

In this example of the " were used this reported incorrectly but if we changed it to this:

/usr/local/nagios/libexec/check_snmp_storage_wizard.pl -H XXX -C DCWest --v2c -m '^/$' -w 80 -c 95 -f

Through the web interface this reports correctly. Were still figuring out if this is an issue with the wizard or so as we've been using the wizard for our configurations for a while now However this fix corrects it.

Thanks for following up and providing the details on what you did to resolve the issue. I will lock this one up.

Perry