The client restarted the servers that are hubs and now one of the secondary servers appears as not secure and some of his java probes give error and do not start.
We have tried restarting both the nimsoft service on the primary hub and on the secondary one which is giving error. But the result has not been successful.
2023-01-09 10:25:08.438 [main] FATAL nimbus.NimProbe - (12) login failed, Received status (12) on response (in sendRcvLogin) for cmd = 'login'
2023-01-09 10:25:08.438 [main] ERROR engine.Engine - Engine main Received status (12) on response (in sendRcvLogin) for cmd = 'login'
com.nimsoft.nimbus.NimStatusCodeException: Received status (12) on response (in sendRcvLogin) for cmd = 'login'
at com.nimsoft.nimbus.NimSessionBase.sendRcvLogin(NimSessionBase.java:732) ~[nimsoft-SDK-9.1.3.jar:9.1.3]
at com.nimsoft.nimbus.NimSessionBase.login(NimSessionBase.java:120) ~[nimsoft-SDK-9.1.3.jar:9.1.3]
at com.nimsoft.nimbus.NimSessionBase.login(NimSessionBase.java:60) ~[nimsoft-SDK-9.1.3.jar:9.1.3]
at com.nimsoft.nimbus.NimProbeBase.login(NimProbeBase.java:430) ~[nimsoft-SDK-9.1.3.jar:9.1.3]
at com.nimsoft.monitoring.engine.EngineProbe.login(EngineProbe.java:27) ~[dme_core-2.5.10.jar:?]
at com.nimsoft.nimbus.NimProbeBase.nimAttachProbe(NimProbeBase.java:303) ~[nimsoft-SDK-9.1.3.jar:9.1.3]
at com.nimsoft.nimbus.NimProbe.initSubscribe(NimProbe.java:572) ~[nimsoft-SDK-9.1.3.jar:9.1.3]
at com.nimsoft.nimbus.NimProbe.doForever(NimProbe.java:416) ~[nimsoft-SDK-9.1.3.jar:9.1.3]
at com.nimsoft.monitoring.engine.Engine.doit(Engine.java:263) ~[dme_core-2.5.10.jar:?]
at com.nimsoft.monitoring.engine.Engine.main(Engine.java:164) [dme_core-2.5.10.jar:?]
at com.nimsoft.monitoring.baseline.BaselineEngineImpl.main(BaselineEngineImpl.java:222) [BaselineEngine-20.10.jar:?]
2023-01-09 10:25:08.454 [ Thread-4] INFO SCRIPTLOG - Closing 7 File Caches
This applies to automated_deployment_engine probe as well.
In testing, once the same controller environment variable was added:
NIM_PROBE_CRYPTO_MODE = AES_128
...and the robot was restarted, then the same java probes failed and the hub in IM displays (NO SECURITY).
To resolve the problem with the select java probes and the NO SECURITY message for the hub in IM:
In IM, deactivate the following probes:
Rt-click and delete the probes.
Then delete the probe folders from the specific hub’s file system to be sure they are gone.
Delete the environment variable from the controller environment:
NIM_PROBE_CRYPTO_MODE = AES_128
Then restart the robot.
Then Choose Security->Validate for ALL probes including the controller, hdb, spooler, to get rid of the (NO SECURITY) tag/message.
Redeploy (from scratch) the probes: