Nagios Support Forum

Quick recap: Once the first update attempt fails (assuming the libssh2 library successfully builds & installs), perform a follow up and it should complete successfully. If you want to avoid the initial failure, this approach works (thanks to Nagios Support): cd /tmp rm -rf nagiosxi xi*.tar.gz wg...

Going to perform a fresh installation of Nagios XI 2024R1.4.3 on a new RHEL 8 instance and then attempt an update to 2024R1.4.4. That was enough to reproduce the issue, both when using the web UI and when using the manual approach: cd /tmp rm -rf nagiosxi xi*.tar.gz wget http://assets.nagios.com/do...

I diffed the copy of the "upgrade" script between the 1.4.3 and 1.4.4 releases. I suspect the problem is here (still digging): # # Special handling for RHEL 8 systems to get libssh2 1.10.0 # if [ "$dist" == "el8" ]; then wget https://libssh2.org/download/libssh2-1.10.0....

The 2024R1.4.3 to 2024R1.4.4 update completed successfully on an instance created from an OVA import (using nagiosxi-2024R1.4.3-OVA.zip). The specific error we're encountering suggests that the upgrade script isn't finding the subcomponents/xiwizards subdirectory path within the decompressed xi-2024...

Eric, It's not just you. I encountered the same error this AM when I attempted to update our Nagios XI instance from 2024R1.4.3 to 2024R1.4.4. Our Nagios XI host is RHEL 8 with the latest updates applied. At this point rolling back (as I did) and then submitting a trouble ticket is probably the only...

Does anyone know if there's a way to send 1 notification that basically says "hey there's a problem, go check it out" no matter what or how many host(s) or service(s) triggers the alert It sounds like you probably want to setup a dependency so that if the specified host & service is d...

should I rewrite all my nagios agents with golang ? That's a significant task to pursue. I'd instead suggest looking at the smallest usable plugin you can create and implement that. As you gain confidence you can implement more complex plugins. I took a similar path and learned a lot from the proce...

YUDI wrote:Hi,
and from Nagios server I got warning message "could not fetch information from server".

Can you connect to port 12489/tcp from the Nagios server?

I recommend using nmap to test this if you haven't already.

For example:

I'd continue the troubleshooting efforts by checking DNS results, using curl and/or a CLI browser like lynx and other tooling to verify connectivity between the Nagios instance you're trying to fix and the website you'd like to monitor. I'd also check whether apparmor or selinux are getting in the w...

That output is from the non fully functional nagios server. Thanks for clarifying. Are you talking about on my local firewall? I was referring to a local firewall on the snapgeek.com host (which nmap reports as 99.198.101.250) or anything that might be between the non-functioning Nagios server and ...