We are seeing this phenomenon right after a hubsec_update fails:
Logs look something like this:
Apr 26 01:15:56:749 [32060] hub: Queue sender thread for 't_6' stopping
Apr 26 01:15:56:791 [49256] hub: Queue sender thread for 't_5' stopping
Apr 26 01:15:56:848 [58980] hub: Queue management thread for 't_6' stopping
Apr 26 01:15:56:890 [24688] hub: Queue management thread for 't_5' stopping
Apr 26 01:16:55:057 [45560] hub: nimSessionWaitMsg: got error on client session: 10054
Apr 26 01:16:55:057 [45560] hub: ihubrequest: nimSessionRequest 'hubsec_update' failed: communication error (192.168.xx.***:48002)-/mydomain/h-nimhub-pos-1/h-nimhub-pos-1/hub (2)
Apr 26 01:16:55:057 [45560] hub: hub_send_event_down - /mydomain/h-nimhub-pos-1
Apr 26 01:16:55:057 [45560] hub: hub_send_event_down - child /mydomain/otherhub is also down
Apr 26 01:16:55:057 [45560] hub: HUB SEC: update h-nimhub-pos-1 failed (communication error)
Apr 26 01:17:33:169 [30188] hub: passive robot thread - finished
Before I go into to much detail, wondering if others are seeing this issue. We have been seeing this with Hub 7.63/7.63/7.71 and controller 7.70