Re: haproxy stops responding to maskable signals

❦ 1 mai 2016 22:31 +0300, Alexander Piavlo  : > Then trying to gracefully reload haproxy often it fails to reload > saying that it cannot bind to sockets. From what i see the old process > does not close the listening sockets, and thus replacement process > fails. Trying to send old haproxy proc

haproxy stops responding to maskable signals

Then trying to gracefully reload haproxy often it fails to reload saying that it cannot bind to sockets. From what i see the old process does not close the listening sockets, and thus replacement process fails. Trying to send old haproxy process SIGTTOU and actualy any other maskable signal does no

Re: Erroneous error code on wrong configuration.

Hi, Am 01.05.2016 um 18:18 schrieb Jonathan Matthews: > frontend my_frontend > bind :80 > acl global hdr(host) -i blablabla > use_backend my_backend if global > backend my_backend > server google www.google.com:80 Given that you don't alter the Host

Re: Erroneous error code on wrong configuration.

On 29 Apr 2016 11:29, "Mayank Jha" wrote: > > I am facing the following in haproxy 1.5. I get the following error, with error code "SC" which is very misleading, for the below mentioned config. Why do you think it's misleading? > haproxy[6379]: 127.0.0.1:53010 [29/Apr/2016:12:05:40.552] my_front