fabio route not removed after consul deregister

[strarsis]

When running the demo server, it registers itself in consul, being listed by consul as healthy.

$ curl http://localhost:8500/v1/catalog/services

{"consul":[],"consul-server-8500":[],"fabio":[],"fabio-9998":[],"fabio-9999":[],"svc-a":["urlprefix-domain.com/foo"]}

$ curl http://localhost:8500/v1/catalog/service/svc-a

[{"Node":"74bd1b630c8d","Address":"172.17.0.2","ServiceID":"svc-a-172.17.0.1:5000","ServiceName":"svc-a","ServiceTags":["urlprefix-domain.com/foo"],"ServiceAddress":"172.17.0.1","ServicePort":5000}]

Fabio also correctly adds the route to routing table, also listed in fabio web gui.

1   svc-a   domain.com  /foo    http://172.17.0.1:5000/ 100%

When the demo server is shut down (Ctrl+c), it reports that it deregistered itself in consul:

2015/12/07 18:35:16 Deregistered service "svc-a" in consul

And indeed, consul doesn't list the demo server anymore:

$ curl http://localhost:8500/v1/catalog/services

{"consul":[],"consul-server-8500":[],"fabio":[],"fabio-9998":[],"fabio-9999":[]}

$ curl http://localhost:8500/v1/catalog/service/svc-a

[]

However, in fabio web gui, the route is still listed:

1   svc-a   domain.com  /foo    http://172.17.0.1:5000/ 100%

[magiconair]

Can you please post the fabio log? It should note the change in the health and service status and print the generated routing table.

[magiconair]

Also, since you're using docker could you describe how you are running the individual applications right now? What is running where and can they all talk to each other on the addresses and ports you've configured ...

[strarsis]

https://github.com/strarsis/consul-fabio-example/

[magiconair]

@strarsis The logs are more helpful at this point

[strarsis]

Log file attached: log.txt

[magiconair]

I think the confusion comes from the registrator. You don't need the registrator for registering either fabio or the demo service. They are both capable of registering themself. Try removing the registrator from your setup and just run the binaries. That should work.

[strarsis]

Thank you for your answer.
I removed the registrator service (and also ensured that it has been really stopped + removed),
but the route still persists in the fabio routing table.

consulfabioexample_consulx1_1   /bin/consul agent -server  ...   Up      8300/tcp, 8301/tcp, 8301/udp, 8302/tcp, 8302/udp, 8400/tcp, 0.0.0.0:8500->8500/tcp, 8600/tcp, 8600/udp
consulfabioexample_fabio_1      /fabio -cfg /etc/fabio/fab ...   Up      0.0.0.0:9998->9998/tcp, 0.0.0.0:9999->9999/tcp

I updated the example repo so it can be directly tested.
https://github.com/strarsis/consul-fabio-example/blob/master/docker-compose.yml

[magiconair]

I think this a duplicate of issue #23. fabio does not flush the last route. I'll release a 1.0.7 to fix this properly.