BUG/MINOR: tcpcheck: Don't rearm the check timeout on each read
The check timeout is used to limit a health-check execution. By default
inter timeout is used. But when defined the check timeout is used. In this
case, the inter timeout (or connect timeout) is used for the connection
establishment only. And the check timeout for the health-check
execution. Thus, it must be set after a successfull connect. It means it is
rearm at the end of each connect rule.
This patch with the previous one (BUG/MINOR: http-check: Use right condition
to consider HTX message as full) should solve the issue #991. It must be
backported as far as 2.2. On the 2.3 and 2.2, there are 2 places were the
connection establishement is handled. The check timeout must be set on both.
diff --git a/src/tcpcheck.c b/src/tcpcheck.c
index 513170a..15d4a25 100644
--- a/src/tcpcheck.c
+++ b/src/tcpcheck.c
@@ -1206,6 +1206,10 @@
out:
if (conn && check->result == CHK_RES_FAILED)
conn->flags |= CO_FL_ERROR;
+
+ if (ret == TCPCHK_EVAL_CONTINUE && check->proxy->timeout.check)
+ check->task->expire = tick_add_ifset(now_ms, check->proxy->timeout.check);
+
return ret;
}
@@ -2040,9 +2044,6 @@
case TCPCHK_ACT_EXPECT:
check->current_step = rule;
if (must_read) {
- if (check->proxy->timeout.check)
- check->task->expire = tick_add_ifset(now_ms, check->proxy->timeout.check);
-
eval_ret = tcpcheck_eval_recv(check, rule);
if (eval_ret == TCPCHK_EVAL_STOP)
goto out_end_tcpcheck;