| Table of Contents | ||||
|---|---|---|---|---|
|
...
opHA uses user/password to access the registry data from the poller, but once the poller has been discover, it uses a token for authentication. So, we should have enabled the authentication method "token" in the poller.
Check if in om<omk_dir>/conf/opCommon.nmis json we have the following (Being X 1, 2 or 3, not matter the order):
...
From the Primary, we can initiate discovery discovery of a peer using the url url https://servername. (using SSL/TLS).
...
This can be set in <omk_dir>/conf/opCommon.nmis json in the poller:
| Code Block |
|---|
"opha_url_base" : "https://servername.domain.com", |
...
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.
...
Ensure that the opHA API user is configured to be the same as the peer setup, the user should exist in the NMIS Users.nmis file and have permissions assigned, by default this is set to omkapiha, check /usr/local/omk/<omk_dir>/conf/opCommon.json
| Code Block |
|---|
"opha_api_user": "omkapiha", |
...
In the primary server add the following configuration option to /usr/local/omk<omk_dir>/conf/opCommon.json in the opHA section.
...