Closed fwkz closed 3 years ago
fabio leaves dangling ports from deregistered services that used TCP Dynamic Proxy
fabio
fabio:1.5.14-go1.15
FABIO_PROXY_ADDR=":9999,0.0.0.0:0;proto=tcp-dynamic;refresh=5s"
netstat -tulpn | grep fabio nomad-1: Tue Oct 27 16:37:20 2020
tcp6 0 0 :::31130 ::: LISTEN 29060/fabio tcp6 0 0 :::24604 ::: LISTEN 29060/fabio tcp6 0 0 :::9998 ::: LISTEN 29060/fabio tcp6 0 0 :::9999 ::: LISTEN 29060/fabio
3. Deregister one of the consul services. Port `31130` is dangling, despite the fact that the underlying service is deregistered and no longer visible on Fabio UI (http://foobar.fabio.ui:9998/routes)
4. Restart `fabio` container to see if it will release ports and start properly.
tcp6 0 0 :::24604 ::: LISTEN 29060/fabio tcp6 0 0 :::9998 ::: LISTEN 29060/fabio tcp6 0 0 :::9999 :::* LISTEN 29060/fabio
I'm seeing the same issue using tcp-dynamic as well. Any way this can be fixed soon?
Abstract
fabio
leaves dangling ports from deregistered services that used TCP Dynamic ProxySteps to reproduce
fabio:1.5.14-go1.15
docker container withFABIO_PROXY_ADDR=":9999,0.0.0.0:0;proto=tcp-dynamic;refresh=5s"
and host networking.tcp6 0 0 :::31130 ::: LISTEN 29060/fabio tcp6 0 0 :::24604 ::: LISTEN 29060/fabio tcp6 0 0 :::9998 ::: LISTEN 29060/fabio tcp6 0 0 :::9999 ::: LISTEN 29060/fabio
netstat -tulpn | grep fabio nomad-1: Tue Oct 27 16:37:20 2020
tcp6 0 0 :::31130 ::: LISTEN 29060/fabio tcp6 0 0 :::24604 ::: LISTEN 29060/fabio tcp6 0 0 :::9998 ::: LISTEN 29060/fabio tcp6 0 0 :::9999 ::: LISTEN 29060/fabio
netstat -tulpn | grep fabio nomad-1: Tue Oct 27 16:37:20 2020
tcp6 0 0 :::24604 ::: LISTEN 29060/fabio tcp6 0 0 :::9998 ::: LISTEN 29060/fabio tcp6 0 0 :::9999 :::* LISTEN 29060/fabio