We are unable to access the secondary hub. Getting the below error...But we are able to telnet to the primary and tunnel hubs without any issue. Recycle of robot/hub had no effect, restart no effect. The secondary hub normally connects to the Tunnel Server (Linux).
hub log showed:
Feb 29 00:02:44:445  hub: nimSession - failed to connect session to 10.xx.xxx.xx:48000, error code 10060
Feb 29 00:02:44:445  hub: TSESS-P-200142-0 [UIM-xxx-TUN-HUB1-xx] could not connect locally to <nimbus_address> (10.xx.xxx.xx/48000)
Feb 29 00:02:44:445  hub: TSESS-P-200142-0 sent error message response
Feb 29 00:02:51:460  hub: nimSession - failed to connect session to xx.xx.xx.xx:48000, error code 10060
Feb 29 00:02:51:460  hub: TSESS-P-200143-1 sent error message response
Feb 29 00:03:00:103  hub: Got STOP command from 10.xxxxxxxxxx
Feb 29 00:03:00:103  hub: main: nimSessionWait rc =4
Feb 29 00:03:00:248  hub: thread shutdown
Feb 29 00:03:01:234  hub: CORE exit
Feb 29 00:03:04:116  hub: EXIT HUB: hub shutdown
Feb 29 00:03:04:116  hub: Waiting for tunnel to terminate ...
Feb 29 00:03:04:116  hub: Waited for 0 seconds for tunnel to terminate (OK)
hub was pingable
telnet to the robot port 48000 was successful but not the hub at 48002
But when trying to resolve it, we get non-existent domain and we noted that the other Secondary hubs were 100% resolvable in AWS.
*** awsxxxxxxx.dxxx.com can't find xxxxxxxHUB: Non-existent domain
We checked 3 other Secondary hubs in AWS and they CAN be resolved with no issue.
- Unknown, perhaps something changed in the aws ec2 instance
Release : 8.51
Component : UIM - HUB
Windows 2012 R2