-
Notifications
You must be signed in to change notification settings - Fork 2
Bind address already in use #118
Comments
Maybe the ports are temporarily unavailable and we don’t give the chance for them to become available. Adding a restart delay in snap (snapcraft's |
Got the same error locally. The port wasn't used by any process when I checked but it looks like core-command restarted 10 times within 10 seconds before (systemd) giving up.
|
It happens again in GitHub action test. core-data port 59880 is busy. There is no restart attempt:
|
Another solution is to start the failed services manually, while waiting 180 seconds for the them to become available. |
Port 44444 is occasionally occupied as well:
|
Port 44444 is not available: #207 (comment) |
We may be able to find the root cause by adding a check before starting services to:
|
Since the services are now all disabled by default, we have the chance to set EDGEX_STARTUP_INTERVAL before starting them for the first time, to slow down the restart intervals suggested in #118 (comment). The downside of doing that is the reliance on a feature which gets tested only later on as part of the same testing suite. |
Tests occasionally fail on Github because the bind address with default ports isn’t available. It isn’t clear if there is an error in services or if the ports are used by some other processes. We’ve seen this for 59880 (core data), 59882 (core command).
When this happens, the services restart very quickly and then disable. This is because the default restart delay from systemd is 100ms without any increments, unlike docker. See systemd/systemd#6129
The attached logs shows core command restarting 9 times in 7 seconds before being permanently stopped:
Example test result and logs:
Related issue in tests: #79, where test port 33333 is not available.
The text was updated successfully, but these errors were encountered: