Nagios Support Forum

Thanks, that works

It's happening for pre-existing Services which have been happily been running for years, and all of the ones I've checked so far. I've seen that when pressing the "Run Check Command" button it makes a request along the lines of https://<servername>/nagiosxi/includes/components/ccm/command_...

In 2026R1 when trying to run the "Run Check Command" for in the config for Services, we get:- ERROR: Invalid host address nagiosxi_error.png I've been through and checked the Host config, and it's the same thats worked for the last few years, without issue. Host Address is a valid and work...

Our Qualys scans have alerted us to a vulnerability in the version of Google Chrome installed via the 2026R1 offline install for redhat, and we need to patch, can I manually upgrade Google Chrome to the latest Google current stable?

We have a RedHat 8 server running 2024R2.2 (and php 8.1) in a secure environment which needs offline upgrades. I have just tried upgrading to 2024R2.2.1, it seemed successful but does not show in the frontend or in /usr/local/nagiosxi/var/xiversion I tried following the instructions on https://suppo...

I've tried this and you need to move into the offline-nagiosxi folder. The commands run, but still no change to the version number.

Thank you, I'll keep an eye out

Trying to do an offline upgrade from 2024R1.1.5 to 2024r1.3.2. I removed the php files from offline-nagiosxi directory as we need to use a currently supported PHP already installed # yum list installed | grep ^php.x86_64 php.x86_64 8.1.31-1.el8.remi @pfs_8_php81 and then in the offline-nagiosx direc...

Removing the nagiosim worked, and I've just upgraded to 5.11.2. But the upgrade our file age checks, complaing that You must specify files to check on with '-F' I compared the new command to one from a backup taken moments before the upgrade, and the new one is definately broken. Reverting the comma...

I just did an upgrade from 5.10.0 to 5.11.2 and it broke our file age checks with the same error message. I compared the new command to one from a backup taken moments before the upgrade, and the new one is definately broken. Reverting the command fixed the issue. ### old ### define command { comman...