Thanks for the answer, as written in http://www.mgoff.in/2010/04/18/haproxy-reloading-your-config-with- minimal-service-impact/ "The end-result is a reload of the configuration file which is not visible by the customer"
But in our case it leads to unbinding from all ports and finishing haproxy process. Can this issue related to rpm build options? RPM build log is https://build.opensuse.org/package/rawlog?arch=x86_64&package=haproxy-1.5&project=server%3Ahttp&repository=openSUSE_12.2 -- Best regards, Eugene Istomin On Thursday 07 February 2013 07:28:17 Willy Tarreau wrote: > Hello Eugene, > > On Wed, Feb 06, 2013 at 08:29:33PM +0200, Eugene Istomin wrote: > > Hello, > > > > We have problem with reload/HUP: > > if i run #/usr/sbin/haproxy -D -f /etc/haproxy/haproxy.cfg -p > > /var/run/haproxy.pid -sf $(cat /var/run/haproxy.pid) - haproxy process is > > shutting down and exit > > This is the intended behaviour, it unbinds from its ports so that the new > process can bind, then waits for all existing connections to terminate > and leaves. Isn't it what you're observing ? What would you have expected > instead ? > > Willy
