-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Submit api "Network.Socket.bind: resource busy (Address in use)" #5985
Comments
Solution: the But I still think that it shouldn't be a stopper. Maybe there should be a warning, like the Node does, but not a crash. |
We are able to reproduce the issue as reported when running multiple node instances but using different port numbers. Proper error messages or documentation should be provided to include metrics-port, or even better; we should be able to run in parallel with just enough configuration. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
pewpew |
External
Area
Other Any other topic (Delegation, Ranking, ...).
Summary
When trying to run two instances(preprod+preview) of cardano-submit-api with the same IP but different ports, one of them throws the error:
Network.Socket.bind: resource busy (Address in use)
.Steps to reproduce
Expected behavior
The check for availability should take the port into account. Both instances should be able to run in parallel.
System info (please complete the following information):
cardano-node 9.1.1 - linux-x86_64 - ghc-8.10
Additional context
Two cardano-node instances for different networks are running on 127.0.0.1 on different ports. The cardano-submit-api instances are also running on 127.0.0.1 on different ports. No matter the order in which they are started, only the one that was started first will work. I don't remember this behavior occurring in previous versions.
The text was updated successfully, but these errors were encountered: