Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-28 Thread Willy Tarreau
On Tue, Apr 28, 2020 at 09:37:29PM +0200, William Dauchy wrote: > On Tue, Apr 28, 2020 at 8:50 PM Willy Tarreau wrote: > > I've pushed the fix below now: > > > > ca39747dcf ("BUG/MEDIUM: mux-h1: make sure we always have a timeout on > > front connections") > > > > Next time you rebuild, it

Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-28 Thread William Dauchy
On Tue, Apr 28, 2020 at 8:50 PM Willy Tarreau wrote: > So just to let you know, we could finally nail the issue down to a > change I did on mux-h1 at the end of dev4 (so dev5 is also affected). > Only front connections dying in a dirty way were affected (i.e. users > disappearing from the net

Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-27 Thread Willy Tarreau
On Mon, Apr 27, 2020 at 11:32:15PM +0500, ??? wrote: > How haproxy.org is managed, some manual update? Can we run git master there? Yep the upgrade is manual, with an automatic revert to the previous version in case of sudden death (has happened quite a few times in the past, not much on

Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-27 Thread Willy Tarreau
Hi William, On Mon, Apr 27, 2020 at 08:34:48PM +0200, William Dauchy wrote: > If this can help, the issue is possibly between dev5 and dev6. We have > been following quite closely the dev releases, but we had to revert > from dev6 to dev5 as it produced issues on our side - where it is >

Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-27 Thread William Dauchy
Hello Willy, On Mon, Apr 27, 2020 at 7:29 PM Willy Tarreau wrote: > just a quick note, be careful with -dev6, monitor your FDs from time > to time. Today it caused an outage on haproxy.org after all FDs were > in use. Sadly we had skipped a number of -dev in the past, jumping > from something

Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-27 Thread Илья Шипицин
How haproxy.org is managed, some manual update? Can we run git master there? On Mon, Apr 27, 2020, 10:30 PM Willy Tarreau wrote: > Hi all, > > just a quick note, be careful with -dev6, monitor your FDs from time > to time. Today it caused an outage on haproxy.org after all FDs were > in use.

Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-27 Thread Willy Tarreau
Hi all, just a quick note, be careful with -dev6, monitor your FDs from time to time. Today it caused an outage on haproxy.org after all FDs were in use. Sadly we had skipped a number of -dev in the past, jumping from something between dev2 and dev3 to dev6, so the breakage might have happened

Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-17 Thread Willy Tarreau
On Sat, Apr 18, 2020 at 02:05:40AM +0200, Tim Düsterhus wrote: > Willy, > > Am 17.04.20 um 14:51 schrieb Willy Tarreau: > > accepted the incoming connection. A new "linux-musl" target was added to > > the makefile because I believed I was the only one using it but I'm not, > > so this can

Re: [ANNOUNCE] haproxy-2.2-dev6

2020-04-17 Thread Tim Düsterhus
Willy, Am 17.04.20 um 14:51 schrieb Willy Tarreau: > accepted the incoming connection. A new "linux-musl" target was added to > the makefile because I believed I was the only one using it but I'm not, > so this can slightly help Docker users. This is in use by the 'haproxy' image of the Docker

[ANNOUNCE] haproxy-2.2-dev6

2020-04-17 Thread Willy Tarreau
Hi, HAProxy 2.2-dev6 was released on 2020/04/17. It added 88 new commits after version 2.2-dev5. It's a bit late as I would have preferred to emit that one earlier, but anyway now it's available. The changes are mostly split into 4 categories: - bug fixes: 22 bugs were fixed since 2.2-dev5.