-
Notifications
You must be signed in to change notification settings - Fork 110
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
gxensemble: fails to start when registry socket file exists #1106
Comments
I think it would be best to clean up the socket on exit. @vyzo is there a good way to go about handling that? |
On further investigation, it seems the issue is in signal handling. What's the general philosophy for handling signals in Gerbil? |
we can install but i think the right way is to introduce some sort of exit handler -- some form of at-exit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running the ensemble registry, if you use the default unix socket and stop the process and restart it, it fails with the following:
This is likely because
socket-bind
expects the file to not exist and fails at the OS level when it does.There's a couple of different ways we can fix this:
If we go with the second option, we will need a second way to ensure we don't have multiple registry processes listening on the same socket.
The text was updated successfully, but these errors were encountered: