haproxy check has 82 warnings, 3 notices

haproxy check (on lb1 test2) gives 82 warnings and 3 notices:

# haproxy -c -- /etc/haproxy/*.cfg
[NOTICE]   (2410509) : haproxy version is 3.0.18-1~bpo12+1
[NOTICE]   (2410509) : path to executable is /usr/sbin/haproxy
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:80] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:81] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:85] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:86] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:88] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:89] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:93] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:95] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:97] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:99] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:102] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:103] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:171] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:172] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:175] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:177] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:178] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:180] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:181] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:185] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:187] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:189] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:191] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:194] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:195] : a 'http-request' rule placed after a 'use_backend' rule will still be processed before.
[WARNING]  (2410509) : config : missing timeouts for backend 'dummy_backend'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'dummy_backend_restricted'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'engine_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'profile_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'diyidp_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'demosp_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'static_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'lifecycle_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'metadata_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'engine_api_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'teams_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'oidc_playground_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'voot_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'pdp_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'aa_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'link_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'manage_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'oidcng_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'myconext_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'account_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'servicedesk_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'mujina-sp_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'mujina-idp_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'minio_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'minioapi_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'spdashboard_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'stats_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'dashboard_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'selfservice_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'tiqr_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'ra_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'azuremfa_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'webauthn_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'gateway_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'middleware_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'monitoring_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'cadvisor_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'welcome_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'invite_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'mock_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'sbs_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'meta_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'eduid_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'openconextaccess_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'midproxy_be'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for backend 'ldap_servers'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : missing timeouts for frontend 'stats'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : 'http-request' rules ignored for frontend 'stats' as they require HTTP mode.
[WARNING]  (2410509) : config : missing timeouts for frontend 'internet_ip'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:71] : 'option httplog' not usable with frontend 'local_ip' (needs 'mode http'). Falling back to 'option tcplog'.
[WARNING]  (2410509) : config : missing timeouts for frontend 'local_ip'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : log format ignored for frontend 'local_ip' since it has no log address.
[WARNING]  (2410509) : config : missing timeouts for frontend 'internet_restricted_ip'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : parsing [/etc/haproxy/haproxy_frontend.cfg:162] : 'option httplog' not usable with frontend 'localhost_restricted' (needs 'mode http'). Falling back to 'option tcplog'.
[WARNING]  (2410509) : config : missing timeouts for frontend 'localhost_restricted'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING]  (2410509) : config : log format ignored for frontend 'localhost_restricted' since it has no log address.
[WARNING]  (2410509) : config : log format ignored for proxy 'ldap' since it has no log address.
[NOTICE]   (2410509) : config : config: Can't open global server state file '/var/lib/haproxy/state': No such file or directory

Start by running haproxy -c -- /etc/haproxy/*.cfg on the test load balancer and review the reported rule-order and backend-timeout warnings. Inspect the HAProxy configuration templates or generated files responsible for those entries; done means the configuration check no longer reports these warnings while preserving the intended routing behavior.