I'm not using peers, it's a feature that I've discovered as you mentionned it, seems worth the try.
I'll upgrade to the latest bpo package from Vincent's repository and see if it fixes my issue, I'll get back to you if it succeeds or not. Thank's Will. Le 01/08/2017 à 11:32, Willy Tarreau a écrit : > On Tue, Aug 01, 2017 at 10:49:20AM +0200, Arnaud B. wrote: >> thank's Vincent. >> >> Unfortunately, I already am on the latest upstream (not backport though) : >> >> $ apt-get update -qq; apt-cache madison haproxy; dpkg -l|grep -i haproxy >> haproxy | 1.7.8-1~bpo9+1 | http://debian.mirrors.ovh.net/debian >> stretch-backports/main amd64 Packages >> haproxy | 1.7.8-1~bpo9+1 | http://ftp.fr.debian.org/debian >> stretch-backports/main amd64 Packages >> haproxy | 1.7.5-2 | http://debian.mirrors.ovh.net/debian >> stretch/main amd64 Packages >> haproxy | 1.7.8-1~bpo9+1 | http://debian.mirrors.ovh.net/debian >> stretch-backports/main Sources >> haproxy | 1.7.5-2 | http://debian.mirrors.ovh.net/debian >> stretch/main Sources >> ii haproxy 1.7.5-2 >> amd64 fast and reliable load balancing reverse proxy >> ii vim-haproxy 1.7.5-2 >> all syntax highlighting for HAProxy configuration files >> >> This stale process issue is quite a mystery atm. > Well, I don't know if you're using peers, but a peers bug causing stale > processes to stay up during reloads was fixed between 1.7.5 and 1.7.8. > It's very likely the same one you're experiencing. And by the way, don't > bother with the UDP socket, it's just the logs. > > As a rule of thumb, you should always use Vincent's latest backports > related to the stable branch you're working on. The packages in your > distro will not contain all fixes, only the ones considered the most > critical, but Vincent takes a great care of maintaining up-to date > versions which are more suitable for production. You can check here > for the available versions : https://haproxy.debian.net/ > > Thus in your case, switching to the 1.7.8 backport seems to make sense. > > Cheers, > Willy
