3da2b63274
When an async connect() fails in sock_conn_check(), it returns an errno that will not be retrieved later by a subsequent getsockopt(SO_ERROR). The problem is that this errno is then definitely lost. This is visible in the 4be_1srv_smtpchk_httpchk_layer47errors regtest that fails on certain systems (e.g. glibc 2.31 on arm32 running Linux 6.1), where the connect() error is systematically lost and the "Connection refused" is never seen in the check status. It also matches a few random reports of the past indicating that the connection error was sometimes not reported in the stats page in front of a down server. Ideally we should store errno in connections as soon as the error is seen. However this would require significant changes that are not acceptable yet for 3.4 nor stable releases. A more acceptable fix is to make use of the extra CO_ER_* flags set by conn_set_errno() as soon as the error is detected. This will recognize a sufficiently large number of errors and the check status will report them (here we'll have "ECONNREFUSED" in the check). Note that on systems where the error is seen synchronously, we can have "ECONNREFUSED (Connection refused)", but this is not a problem. This fix adds the missing conn_set_errno() call to sock_conn_check(), that is thus sufficient to catch this error. In addition, the two affected regtests were updated to search for ECONNREFUSED here. This might be backported to older releases if users request it, but it is probably not necessary. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
Please refer to the following files depending on what you're looking for:
- INSTALL for instructions on how to build and install HAProxy
- BRANCHES to understand the project's life cycle and what version to use
- LICENSE for the project's license
- CONTRIBUTING for the process to follow to submit contributions
The more detailed documentation is located into the doc/ directory:
- doc/intro.txt for a quick introduction on HAProxy
- doc/configuration.txt for the configuration's reference manual
- doc/lua.txt for the Lua's reference manual
- doc/SPOE.txt for how to use the SPOE engine
- doc/network-namespaces.txt for how to use network namespaces under Linux
- doc/management.txt for the management guide
- doc/regression-testing.txt for how to use the regression testing suite
- doc/peers.txt for the peers protocol reference
- doc/coding-style.txt for how to adopt HAProxy's coding style
- doc/internals for developer-specific documentation (not all up to date)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.