Unable to contact with controller probe with error Failed to connect session to HUBIP:48001, error code 10055, error code 10060
Article ID: 193187
Updated On:
Products
Issue/Introduction
The hub log is full of these errors shown below and Robots are not reporting to the hub.
hub: nimSession - failed to connect session to HUBIP:48001, error code 10055
hub: nimSession - failed to connect session to HUBIP:48001, error code 10055
hub: sockConnect - connect to hubIP 48000 failed 10060
hub: nimSession - failed to connect session to hubIP:48000, error code 10060
hub: nimSession - failed to connect session to hubIP:48000, error code 10060
Environment
- Component : UIM - HUB
Cause
The possible reasons are:
if too many network connections open from the hub side to communicate with the robots, then it gets stuck as ERROR CODE: 10055 which is basically a network related issue.
That's why when the hub is restarted, initially it works fine, then when all connections establish the issue starts occurring again.
Execute the command below to check how many hub-related connections are established.
netstat -an | findstr "<enter filter parameter here>''
Resolution
ERROR CODE: 10055 is a network /system setting related issue :
As If you try to set up TCP connections from ports that are greater than 5000, the local computer responds with above code and
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
The Microsoft article at the url below can help you to change the related registry value:
You receive the error 'WSAENOBUFS (10055)' when you try to connect from TCP ports greater than 5000
Try to keep the number of robots at ~1800 for a single hub as the official limit is 2000.
Feedback
