Hi,
Le 06/02/2016 01:03, Maciej Katafiasz a écrit :
On 5 February 2016 at 16:02, Maciej Katafiasz
<[email protected]> wrote:
Link to the tarball:
https://purestorage.app.box.com/s/nnzqueais46plzd9xfisnmkeab7j9s0y
I will be sending it as an attachment in a separate mail as a followup
to this one, in case the mailing list software scrubs attachments
and/or considers them spam.
And here's the tarball as an attachment
This looks to be concern more consul inside a docker container than a
haproxy itself. But this may explain some similar reports made by other
users recently.
Use the -reap option with consul-template, and haproxy will reload
correctly.
As quick example :
$ docker run --name=haproxy -d --net=host haproxy-bugtest
consul-template -config=/tmp/haproxy.ctmpl.cfg -log-level=debug -reap
$ docker exec -ti haproxy sh
# ps aux
...
16 root 0:00 haproxy -f /etc/haproxy/haproxy.cfg -d -p
/var/run/haproxy.pid -sf
...
# haproxy -f /etc/haproxy/haproxy.cfg -d -p /var/run/haproxy.pid -sf 16
&> /tmp/debug.log&
# ps aux
...
27 root 0:00 haproxy -f /etc/haproxy/haproxy.cfg -d -p
/var/run/haproxy.pid -sf 16
...
=> No more PID 16
--
Cyril Bonté
