Hello,
We are finally attempting to roll out Nagios xi to our production system, but are hitting a dependency conflict with the "rh-postgresql12-postgresql-syspaths-12.7-1.el7 and rh-postgresql12-postgresql-server-syspaths.
We were under the impression that Nagios xi is using MySQL for its backend, and doesn't require postgres, so is this something that can be skipped somehow? We are attempting to install it on a jump server (via yum), which is the only system that has access to the remote systems that are needing it's monitoring. The other service on this system, is Foreman (https://www.theforeman.org)
Nagios xi Install - Postgresql Conflict
-
- Posts: 247
- Joined: Tue Aug 31, 2021 3:25 pm
Re: Nagios xi Install - Postgresql Conflict
Hi EchoUser,
Unfortunately, while mysql or mariadb are the default database the postgresql postgresql-contrib packages are a dependency for Nagiosxi. This is one of the reasons why it is advised only to install Nagios on a clean system with no other applications running. Even if you are able to successfully work around the postgres dependency it will complicate upgrades and cause problems down the road. The installation guide talks about it briefly on page 2:
https://assets.nagios.com/downloads/nag ... -Linux.pdf
Our recommendation would be to install Nagios on a separate internal system/VM that you can access through the jump server via port forwarding or a proxy.
Thanks and Best Regards,
Keith
Unfortunately, while mysql or mariadb are the default database the postgresql postgresql-contrib packages are a dependency for Nagiosxi. This is one of the reasons why it is advised only to install Nagios on a clean system with no other applications running. Even if you are able to successfully work around the postgres dependency it will complicate upgrades and cause problems down the road. The installation guide talks about it briefly on page 2:
https://assets.nagios.com/downloads/nag ... -Linux.pdf
Our recommendation would be to install Nagios on a separate internal system/VM that you can access through the jump server via port forwarding or a proxy.
Thanks and Best Regards,
Keith