today we run into a bug and we did not understand how this goes wrong.
Setup
Galera-Cluster with 3 Node
Icingaweb Server with HA Proxy for Galera Loadbalancing
HAProxy with the Galere Cluster listen on Port 3307
Nagvis Version: 1.9.29-4.el8.noarch
Operating System on all hosts: RHEL8
Bug description
We want to configure NagVis to connect to the port 3307 and not to 3306.
In the config file we can change dbport to 3307 and you can see the 3307 Port in the UI.
BUT the code ignores the port and always try to connect the port 3306.
For a test, we build an MariaDB Slave on the icingaweb system nagvis is installed on.
HA Proxy is running on 3307
MariaDB Slave is running on 3306
Test 1:
Stop mariadb slave
Change the NagVis dbport config to 3307
Results: NagVis is not working (Error Nagios Service is not running)
Test 2:
stop mariadb slave
Change the NagVis dbport config to 3307
Results: NagVis is not working (Error Nagios Service is not running)
start mariadb slave to run on 3306
Results: NagVis is running, NagVis presents in the UI dbport 3307 BUT the connection goes to the slave on 3306 and not to the HA Proxy on port 3307
Test 3:
stop mariadb slave
Change the NagVis dbport config to 12345
Results: NagVis is not working (Error Nagios Service is not running)
start mariadb slave to run on 3306
Results: NagVis is running, NagVis presents in the UI dbport 12345 BUT the connection goes to the slave on 3306 and not to the HA Proxy on port 12345
We also tried to change the default value in the source code to 3307 but same effect, NagVis ignores the port.
In fact we have a setup with over 50.000 Checks and 10.000 Endpoints, so we wont have a local running MariaDB on the NagVis system and we have to use a proxy in front of the Galera Cluster.
Hello,
today we run into a bug and we did not understand how this goes wrong.
Setup
Bug description
We want to configure NagVis to connect to the port 3307 and not to 3306. In the config file we can change dbport to 3307 and you can see the 3307 Port in the UI. BUT the code ignores the port and always try to connect the port 3306.
For a test, we build an MariaDB Slave on the icingaweb system nagvis is installed on. HA Proxy is running on 3307 MariaDB Slave is running on 3306
Test 1:
Test 2:
stop mariadb slave
Change the NagVis dbport config to 3307
Results: NagVis is not working (Error Nagios Service is not running)
start mariadb slave to run on 3306
Results: NagVis is running, NagVis presents in the UI dbport 3307 BUT the connection goes to the slave on 3306 and not to the HA Proxy on port 3307
Test 3:
stop mariadb slave
Change the NagVis dbport config to 12345
Results: NagVis is not working (Error Nagios Service is not running)
start mariadb slave to run on 3306
Results: NagVis is running, NagVis presents in the UI dbport 12345 BUT the connection goes to the slave on 3306 and not to the HA Proxy on port 12345
We also tried to change the default value in the source code to 3307 but same effect, NagVis ignores the port.
In fact we have a setup with over 50.000 Checks and 10.000 Endpoints, so we wont have a local running MariaDB on the NagVis system and we have to use a proxy in front of the Galera Cluster.
Help us to fix this issue, please.
Cheers Andreas