...
In this case, the SSL certificate is likely to be a local certificate authority (CA), or you might be using self-signed SSL certificates, in which case you will need to let the applications know it is OK.
In On the primary server add change the following configuration option to reflect the same as below to <omk_dir>/conf/opCommon.json in the opHA section.
| Code Block |
|---|
"opha_allow_insecure" : "1", |
You may also need to enable the below as well on the primary server:
| Code Block |
|---|
"omk_ua_insecure" : "1", |
After changing restart the daemon.
...
| Code Block |
|---|
"opha_api_user" : "omkapiha", |
Teapot error: error saving node to remote
in the GUI if you observe the following error:
Check the /usr/local/omk/log/opDaemon.log and if you see the following lines:
[debug] current_app_log: bad log, application_key missing
[error] NodeData::update_resource Error creating node in remote. Reason: 418 I'm a teapot
[debug] 418 I'm a teapot (0.127757s, 7.827/s)
Validate that pollers and primary have the same types set in nmis9/conf/Config.nmis for each of the following: 'nodetype_list', 'nettype_list', 'roletype_list'
An easy way to do this is using the patch_config.pl tool:
| Code Block |
|---|
/usr/local/nmis9/admin/patch_config.pl -r /usr/local/nmis9/conf/Config.nmis roletype_list
/usr/local/nmis9/admin/patch_config.pl -r /usr/local/nmis9/conf/Config.nmis nettype_list
/usr/local/nmis9/admin/patch_config.pl -r /usr/local/nmis9/conf/Config.nmis nodetype_list |
If mismatched then update, restart daemons (nmis9d and omkd) then rediscover poller.