-
Notifications
You must be signed in to change notification settings - Fork 37
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
deadlock? #9
Comments
why do you have two different ports listening? Looks like 666 and 667? |
I'm running CaptainHook on Docker with autorestart=true. So to be able to run CaptainHook in multiple containers on the same machine with --net=host Docker, I use
Hence the |
So basically, I think this goes like: bind to 666, crash without releasing the bind, bind on 667. |
PS this is on Ubuntu 14.04 using Go 1.2.1. |
It's deadlocked because the port is in use. Your incrementing script might have a bug? |
Hmm this is running on a machine with only one Docker container running, so the port wasn't in use. I can also see that by the |
it didn't bind to it, that's line 34 in your stack trace. Go is waiting for that port to be freed. |
The text was updated successfully, but these errors were encountered: