Yes from haproxy.debian.net Aug 19 22:09:09 haproxy-2 systemd[1]: Starting HAProxy Load Balancer... Aug 19 22:09:09 haproxy-2 haproxy[1280]: [NOTICE] (1280) : haproxy version is 2.6.3-1~bpo11+1 Aug 19 22:09:09 haproxy-2 haproxy[1280]: [NOTICE] (1280) : path to executable is /usr/sbin/haproxy Aug 19 22:09:09 haproxy-2 haproxy[1280]: [WARNING] (1280) : config : 'option forwardfor' ignored for frontend 'gerrit-ssh' as it requires HTTP mode. Aug 19 22:09:09 haproxy-2 haproxy[1280]: [WARNING] (1280) : config : 'option forwardfor' ignored for backend 'bck-review-ssh' as it requires HTTP mo> 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! 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 Aug 19 22:10:39 haproxy-2 systemd[1]: haproxy.service: start operation timed out. Terminating. Aug 19 22:10:39 haproxy-2 systemd[1]: haproxy.service: Killing process 1282 (haproxy) with signal SIGKILL. Aug 19 22:10:39 haproxy-2 systemd[1]: haproxy.service: Failed with result 'timeout'. Aug 19 22:10:39 haproxy-2 systemd[1]: haproxy.service: Unit process 1282 (haproxy) remains running after unit stopped. Aug 19 22:10:39 haproxy-2 systemd[1]: Failed to start HAProxy Load Balancer. Aug 19 22:10:39 haproxy-2 systemd[1]: haproxy.service: Consumed 1min 30.496s CPU time.
----- Mail original ----- De: "Vincent Bernat" <ber...@luffy.cx> À: "Ionel GARDAIS" <ionel.gard...@tech-advantage.com>, "Willy Tarreau" <w...@1wt.eu> Cc: "haproxy" <haproxy@formilux.org> 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 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 from "journalctl -eu haproxy" should help. -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
