...
Peer cannot be discovered
From the masterPrimary, we can run the discover using the cli tool with debug enabled to get further information:
...
If there is any connectivity error, you can test the connectivity from the poller to the master Primary using curl (This is an example with default credentials):
...
opHA cluster_id already exist!
Check the master Primary and all other pollers nmis configuration for the cluster_id property. It can be found in nmis9/conf/Config.nmis. This one should be unique per server, so in case one of the pollers has a repeated one you can remove the property in the configuration file and nmis will generate a new one.
...
Configuring a poller over https
From the masterPrimary, we can initiate discovery of a peer using the url https://servername. (using SSL/TLS).
But, we will not be able to query the poller as the poller will report it's url as http: . To force the master Primary to use HTTPS to the poller we must have the configuration item opha_url_base set to https otherwise, it won't work.
...
If we set the url to https://servername in the discover, the poller is going to send its registry data to the masterPrimary, and the master Primary will get the correct url_base for the peer from that information.
If the opha_url_base is blank the master Primary will swap the https:// URL for http://
Some data is not updated in the
...
Primary
opHA has a new feature to synchronise only the data that has being added/modified since the last synchronisation. In case some data is not modified, we can perform a force synchronisation, adding some parameters to update only the required data types and nodes:
...