The aforementioned patch adds information on how to check a host's local port range, and how to check if a port is already in use. I reckon we don't need to single out keystone as in Comment 1, since it could happen to any service depending on the configured local port range.
The aforementioned patch adds information on how to check a host's local port range, and how to check if a port is already in use. I reckon we don't need to single out keystone as in Comment 1, since it could happen to any service depending on the configured local port range.