| commit | c31577f32e0094010516a923e9f5e8cc23c23d43 | [log] [tgz] |
|---|---|---|
| author | William Lallemand <wlallemand@haproxy.org> | Tue Jul 26 10:50:09 2022 +0200 |
| committer | William Lallemand <wlallemand@haproxy.org> | Tue Jul 26 10:59:14 2022 +0200 |
| tree | b4fb0ce8e6339414c41779ea2a14215633fdb24c | |
| parent | dc66f2f97d76613d732c49cc326791863b018f0e [diff] |
MEDIUM: resolvers: continue startup if network is unavailable When haproxy starts with a resolver section, and there is a default one since 2.6 which use /etc/resolv.conf, it tries to do a connect() with the UDP socket in order to check if the routes of the system allows to reach the server. This check is too much restrictive as it won't prevent any runtime failure. Relax the check by making it a warning instead of a fatal alert. This must be backported in 2.6.