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 /run/haproxy/admin.sock"
defined in /etc/defaults/haproxy
This is the path referenced in the configuration file
stats socket /run/haproxy/admin.sock mode 660 level admin
However, during the upgrade process, the newly started process is referencing
'sockpair@3'
/usr/sbin/haproxy -sf 1016 -x sockpair@3 -Ws -f /etc/haproxy/haproxy.cfg -p
/run/haproxy.pid
[Unit]
Description=HAProxy Load Balancer
Documentation=man:haproxy(1)
Documentation=file:/usr/share/doc/haproxy/configuration.txt.gz
After=network-online.target rsyslog.service
Wants=network-online.target
[Service]
EnvironmentFile=-/etc/default/haproxy
EnvironmentFile=-/etc/sysconfig/haproxy
BindReadOnlyPaths=/dev/log:/var/lib/haproxy/dev/log
Environment="CONFIG=/etc/haproxy/haproxy.cfg" "PIDFILE=/run/haproxy.pid"
"EXTRAOPTS=-S /run/haproxy-master.sock"
ExecStart=/usr/sbin/haproxy -Ws -f $CONFIG -p $PIDFILE $EXTRAOPTS
ExecReload=/usr/sbin/haproxy -Ws -f $CONFIG -c -q $EXTRAOPTS
ExecReload=/bin/kill -USR2 $MAINPID
KillMode=mixed
Restart=always
SuccessExitStatus=143
Type=notify
# The following lines leverage SystemD's sandboxing options to provide
# defense in depth protection at the expense of restricting some flexibility
# in your setup (e.g. placement of your configuration files) or possibly
# reduced performance. See systemd.service(5) and systemd.exec(5) for further
# information.
# NoNewPrivileges=true
# ProtectHome=true
# If you want to use 'ProtectSystem=strict' you should whitelist the PIDFILE,
# any state files and any other files written using 'ReadWritePaths' or
# 'RuntimeDirectory'.
# ProtectSystem=true
# ProtectKernelTunables=true
# ProtectKernelModules=true
# ProtectControlGroups=true
# If your SystemD version supports them, you can add: @reboot, @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" <ber...@luffy.cx>
À: "Ionel GARDAIS" <ionel.gard...@tech-advantage.com>
Cc: "Willy Tarreau" <w...@1wt.eu>, "haproxy" <haproxy@formilux.org>
Envoyé: Vendredi 19 Août 2022 23:37:47
Objet: Re: [*EXT*] [ANNOUNCE] haproxy-2.6.3
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 change in 2.6.0 (but not in 2.6.3) where "expose-fd
listeners" for stats socket is not needed anymore. Is the line present
in your configuration? (grep admin.sock /etc/haproxy/haproxy.cfg)
What's the output of systemctl cat haproxy?
> Aug 19 22:09:09 haproxy-2 haproxy[1280]: [NOTICE] (1280) : New worker
> (1282) forked
> Aug 19 22:09:09 haproxy-2 haproxy[1280]: [NOTICE] (1280) : Loading success.
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: [WARNING] (1282) : Server
> bck-speedtest/go-v6 is DOWN, reason: Layer4 connection problem, info:
> "Connection>
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: Server bck-speedtest/go-v6 is DOWN,
> reason: Layer4 connection problem, info: "Connection refused", check dur>
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: Server bck-speedtest/go-v6 is DOWN,
> reason: Layer4 connection problem, info: "Connection refused", check dur>
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: [WARNING] (1282) : Server
> bck-nuxeo-arch/nuxeo-arch is DOWN, reason: Layer4 connection problem, info:
> "No r>
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: [ALERT] (1282) : backend
> 'bck-nuxeo-arch' has no server available!
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: Server bck-nuxeo-arch/nuxeo-arch is
> DOWN, reason: Layer4 connection problem, info: "No route to host", check>
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: Server bck-nuxeo-arch/nuxeo-arch is
> DOWN, reason: Layer4 connection problem, info: "No route to host", check>
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: backend bck-nuxeo-arch has no server
> available!
> Aug 19 22:09:09 haproxy-2 haproxy[1282]: backend bck-nuxeo-arch has no server
> available!
> […] // others few backends not responding
> // then
Are these expected?
--
232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON
Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
