On Mon, Aug 22, 2022 at 04:33:51PM +, Bren wrote:
> --- Original Message ---
> On Monday, August 22nd, 2022 at 7:03 AM, William Lallemand
> wrote:
>
> > I'm going to issue a 2.6.4 today with the patch.
>
> Just rolled out 2.6.4 and everything appears to be working as expected now.
--- Original Message ---
On Monday, August 22nd, 2022 at 7:03 AM, William Lallemand
wrote:
> I'm going to issue a 2.6.4 today with the patch.
Just rolled out 2.6.4 and everything appears to be working as expected now.
Thanks!
On Sat, Aug 20, 2022 at 09:56:40PM +0200, Willy Tarreau wrote:
> On Sat, Aug 20, 2022 at 09:36:21PM +0200, Ionel GARDAIS wrote:
> > That was it :
> > - remove the EXTRAOPTS from /etc/default/haproxy
> > - stop the running process referencing -x /run/haproxy/admin.sock on the CLI
> > - upgrade
> >
On Sat, Aug 20, 2022 at 08:50:25PM +, Bren wrote:
> --- Original Message ---
> On Saturday, August 20th, 2022 at 3:43 PM, Vincent Bernat
> wrote:
>
> > Do you have something here too?
>
> Nope. In fact I just removed that from the build.
>
> > This does not match the file shipped b
--- Original Message ---
On Saturday, August 20th, 2022 at 3:43 PM, Vincent Bernat
wrote:
> Do you have something here too?
Nope. In fact I just removed that from the build.
> This does not match the file shipped by HAProxy, but this may explain
> why you also run into this bug.
What
On 2022-08-20 22:35, Bren wrote:
EnvironmentFile=-/etc/default/haproxy
Do you have something here too?
Environment="CONFIG=/etc/haproxy/haproxy.cfg" "PIDFILE=/run/haproxy.pid"
This does not match the file shipped by HAProxy, but this may explain
why you also run into this bug.
On 2022-08-20 21:36, Ionel GARDAIS wrote:
That was it :
- remove the EXTRAOPTS from /etc/default/haproxy
- stop the running process referencing -x /run/haproxy/admin.sock on the CLI
- upgrade
All is OK.
First processes do not list -x on the CLI and a reload spawn a process with -x
sockpair@
S
--- Original Message ---
On Saturday, August 20th, 2022 at 9:50 AM, Willy Tarreau wrote:
> Did you notice if it failed to serve anything and ate CPU from start or
> if it completely started and only then ate CPU ?
It appears to start up normally according to the logs and then it uses 100
On Sat, Aug 20, 2022 at 09:36:21PM +0200, Ionel GARDAIS wrote:
> That was it :
> - remove the EXTRAOPTS from /etc/default/haproxy
> - stop the running process referencing -x /run/haproxy/admin.sock on the CLI
> - upgrade
>
> All is OK.
> First processes do not list -x on the CLI and a reload spawn
original -
De: "Vincent Bernat"
À: "Ionel GARDAIS"
Cc: "Willy Tarreau" , "haproxy"
Envoyé: Samedi 20 Août 2022 20:28:21
Objet: Re: [*EXT*] [ANNOUNCE] haproxy-2.6.3
On 2022-08-20 19:15, Ionel GARDAIS wrote:
> Below is the systemctl cat haproxy output.
On 2022-08-20 19:15, Ionel GARDAIS wrote:
Below is the systemctl cat haproxy output.
Yes, not responding backends was expected, sorry for not specified it.
"expose-fd listeners" was present in the configuration file. Update fails even
after I removed the two keywords.
I have
EXTRAOPTS="-x /
t, @swap, @sync
# SystemCallFilter=~@cpu-emulation @keyring @module @obsolete @raw-io
[Install]
WantedBy=multi-user.target
--
Ionel GARDAIS
Tech'Advantage CIO - IT Team manager
- Mail original -
De: "Vincent Bernat"
À: "Ionel GARDAIS"
Cc: "Willy Tarreau
Hi Bren,
On Sat, Aug 20, 2022 at 02:05:37PM +, Bren wrote:
> I also had to roll back. I compile from source and push out the binary with
> Ansible which hung on reload. I observed an haproxy process running as root
> using 100% CPU. It never restarted - I had to kill the processes.
>
> When I
--- Original Message ---
On Friday, August 19th, 2022 at 3:16 PM, Ionel GARDAIS
wrote:
>
>
> Hi Willy,
>
> I had to rollback to 2.6.2
I also had to roll back. I compile from source and push out the binary with
Ansible which hung on reload. I observed an haproxy process running as r
On Fri, Aug 19, 2022 at 11:37:47PM +0200, Vincent Bernat wrote:
> On 2022-08-19 23:09, Ionel GARDAIS wrote:
> > Aug 19 22:09:09 haproxy-2 haproxy[1280]: [WARNING] (1280) : Failed to
> > connect to the old process socket '/run/haproxy/admin.sock'
> > Aug 19 22:09:09 haproxy-2 haproxy[1280]: [ALERT
On 2022-08-19 23:09, Ionel GARDAIS wrote:
Aug 19 22:09:09 haproxy-2 haproxy[1280]: [WARNING] (1280) : Failed to connect
to the old process socket '/run/haproxy/admin.sock'
Aug 19 22:09:09 haproxy-2 haproxy[1280]: [ALERT](1280) : Failed to get the
sockets from the old process!
There was a
l original -
De: "Vincent Bernat"
À: "Ionel GARDAIS" , "Willy Tarreau"
Cc: "haproxy"
Envoyé: Vendredi 19 Août 2022 22:37:49
Objet: Re: [*EXT*] [ANNOUNCE] haproxy-2.6.3
On 2022-08-19 22:16, Ionel GARDAIS wrote:
> I had to rollback to 2.6.2 after having
On 2022-08-19 22:16, Ionel GARDAIS wrote:
I had to rollback to 2.6.2 after having upgrade to 2.6.3 because systemd was
restarting the haproxy process every 1m30s (on an up-to-date Debian 11)
apt upgrade itself hung while doing the upgrade.
With Debian packages from haproxy.debian.net? Logs fr
aproxy"
Envoyé: Vendredi 19 Août 2022 18:51:25
Objet: [*EXT*] [ANNOUNCE] haproxy-2.6.3
Hi,
HAProxy 2.6.3 was released on 2022/08/19. It added 60 new commits
after version 2.6.2.
This release contains assorted fixes for issues discovered after the
previous 2.6.2 release, and there are quite a fe
19 matches
Mail list logo
