Page Comparison

...

Please, notice that in case the server has nodes already, the nodes should be exported and imported again with localised_ids once the cluster_id was is changed, as the nodes information won't have the same cluster_id attribute and they will be treated as remote nodes (They cannot be edited, or polled, as an example). 

...

Different situations have being been identified causing this issue: 

• If the same node name exist exists in more than one poller, and the configuration item opevents_auto_create_nodes is true, a new Local node will be created in the primary server. This is because, the event is just identified by a node name, and the primary cannot choose with which of the remote nodes assign assigned the event. 
• If there are two Main primary servers: This situation can cause chaos in the environment, as both primaries will change the nodes from the pollers. 
• Also, if some catchall data is duplicated in the primary, we would be looking some nodes as duplicates in opCharts. 

...

Premature Connection Close

The web server closed the connection before the user agent could receive the whole response or that the user agent got destroyed, which forces all connections to be closed immediately.

We can tune the following values to prevent this error to happen: 

In the primary server

If the poller is taking too long to respond, we can increase the value of omkd_inactivity_timeout in <omk_dir>/conf/opCommon.json.

...