I've been running into a problem for a few weeks that I was hoping to see disappear w/ a simple upgrade to 1.6.3.
I'm using consul and it's templating to dynamically expand a backend list which then runs an haproxy reload using the init scripts in the contrib dir. I haven't been able to trace how the situation is triggered,but basically I find haproxy processes that are still listening on their bound sockets long after having received a reload signal via the '-sf' parameter. My first fix was to ensure that reloads weren't happening too fast and potentially stomping on the pid file which would explain a process never getting a signal--so I now have a lock + sleeps for the automatic reload script. No change. What's probably most interesting is that a SIGKILL is necessary to remove the 'stale' processes that are still listening on their sockets (as determined by lsof.) I can supply the config if needed, there is a single listener w/ a pem directory specified if that's helpful. system info: [david@sjc1-b1-4 ~]$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS" [david@sjc1-b1-4 ~]$ uname -a Linux sjc1-b1-4 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
