Error: No socket could be created

Valid for cylc-7.8.8

upon moving to a new node (HPC environment) and testing two simple suites
we are met with

Exception in thread HTTPServer Thread-2:
Traceback (most recent call last):
error: No socket could be created – ((‘XXX.XX.XX.K’, YYYYY): [Errno 99] Cannot assign requested address) – ((‘XXX.XX.XX.K+1’, YYYY): [Errno 99] Cannot assign requested address) …
continue iterating over a list of IP addresses, K+2, …

most likely a node configuration setting for admin types.
I thought I would at least seed the admin efforts with comments from this forum.

Question: where do we start looking?

First, check the Cylc global config setting for the range of ports Cylc can use.

Then, check that those ports are available on the host, and that other processes are not already bound to all of those ports.

Your admin people might need to help with the second bit.

thank you h.
turns out there was a setting in the Cylc global config file that had an hardcoded node value.
i was able to use a different setting and we are ‘all good’ with that one.

1 Like