...
| Code Block |
|---|
opha-cli.pl act=pull data_types=[nodes|latest_data|...] peers=[nodeNames] force=t |
Duplicated nodes
Two different Different situations have being identified causing this issue:
- If the same node name exist 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 of the remote nodes assign 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.
It is possible to check if there are duplicates:
- In opHA GUI in the Main Page in Verify
- In opHA cli with the command:
| Code Block |
|---|
/usr/local/omk/bin/opha-cli.pl act=data_verify |
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.