to this.
Anthony
From: William Lallemand
Sent: Monday, December 11, 2017 3:32 PM
To: Anthony Via
Cc: haproxy@formilux.org
Subject: Re: Testing master-worker reloads on HAProxy 1.8
On Mon, Dec 11, 2017 at 11:03:52PM +, Anthony Via wrote:
> > Did you
On Mon, Dec 11, 2017 at 11:03:52PM +, Anthony Via wrote:
> > Did you try the seamless reload using -x without the master-worker?
>
> I was looking into the "-x" option and it looks like simply adding "expose-fd
> listeners" to my stats socket has fixed this issue for me. Sending SIGUSR2 to
> t
: William Lallemand
Sent: Friday, December 8, 2017 1:54 PM
To: Anthony Via
Cc: haproxy@formilux.org
Subject: Re: Testing master-worker reloads on HAProxy 1.8
> On Wed, Dec 06, 2017 at 10:48:23PM +, Anthony Via wrote:
> > I am testing seamless reloads on HAProxy 1.8.0 using the master-w
> On Wed, Dec 06, 2017 at 10:48:23PM +, Anthony Via wrote:
> > I am testing seamless reloads on HAProxy 1.8.0 using the master-worker
> > model and am running into the following when sending SIGUSR2 to the master
> > process
Sorry I misread, my explanation in the previous post is not correct f
Hello Anthony,
On Wed, Dec 06, 2017 at 10:48:23PM +, Anthony Via wrote:
> ?Hello,
>
>
> I am testing seamless reloads on HAProxy 1.8.0 using the master-worker model
> and am running into the following when sending SIGUSR2 to the master process:
>
>
> [ALERT] 339/222907 (61399) : Starting
?Hello,
I am testing seamless reloads on HAProxy 1.8.0 using the master-worker model
and am running into the following when sending SIGUSR2 to the master process:
[ALERT] 339/222907 (61399) : Starting frontend internal_http: cannot bind
socket [0.0.0.0:80]
[WARNING] 339/222907 (61399) : Reexe
6 matches
Mail list logo