Hello,
As for configuration, yes, as Lukas pointed, "hard-stop-after" is a
right setting, it was designed specifically for such case of long
connections.
If master-worker mode is used, there is also "mworker-max-reloads",
which can help.
https://docs.haproxy.org/3.0/configuration.html#3.1
Hi Jens !
Thanks for detailed explanations !
I've looked a bit, why you have this "Proxy is disabled." message,
when"@!PID shutdown sessions server"is issued.
In simply words, for old worker's backend proxies we set the flag
PR_FL_STOPPED during the reload and it's checked in the handler of
This defect was found by the coccinelle script "unchecked-strdup.cocci".
It can be backported to all supported branches.
---
src/resolvers.c | 12
1 file changed, 12 insertions(+)
diff --git a/src/resolvers.c b/src/resolvers.c
index f8f0c8edf..bff5c290d 100644
--- a/src/resolvers.c
+
This defect was found by the coccinelle script "unchecked-strdup.cocci".
It can be backported to all supported branches.
---
src/ssl_crtlist.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/ssl_crtlist.c b/src/ssl_crtlist.c
index 71fa0a0b1..7d2b1ed12 100644
--- a/src/ssl_crtlist.c
+++
This defect was found by the coccinelle script "unchecked-strdup.cocci".
It can be backported to all supported branches.
---
src/namespace.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/namespace.c b/src/namespace.c
index 9cc85a384..12885cd9f 100644
--- a/src/namespace.c
+++ b/src/
5 matches
Mail list logo