deadlock? about captainhook HOT 7 CLOSED

why do you have two different ports listening? Looks like 666 and 667?

from captainhook.

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

#!/bin/bash

increment=${CAPTAINHOOK_PORT_INCREMENT:-1}
port=${CAPTAINHOOK_PORT:-666}

isfree=$(netstat -tapln | grep $port)
while [[ -n "$isfree" ]]; do
  port=$[port+increment]
  isfree=$(netstat -tapln | grep $port)
done

exec /usr/share/gocode/bin/captainhook -listen-addr 127.0.0.1:$port -configdir /etc/captainhook -echo

Hence the 2014/09/29 19:27:13 Listening on 127.0.0.1:667 line.

from captainhook.

So basically, I think this goes like: bind to 666, crash without releasing the bind, bind on 667.

from captainhook.

PS this is on Ubuntu 14.04 using Go 1.2.1.

from captainhook.

It's deadlocked because the port is in use. Your incrementing script might have a bug?

from captainhook.

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 2014/09/29 19:27:13 Listening on 127.0.0.1:666 line. If the port was in use, it would not have bound to it.

from captainhook.

it didn't bind to it, that's line 34 in your stack trace. Go is waiting for that port to be freed.

from captainhook.