From ca57de3e7b5ea23e9e1ec51cb33637334196b52f Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Fri, 23 Nov 2012 20:08:09 +0100 Subject: [PATCH] BUG/MAJOR: peers: the listener's maxaccept was not set and caused loops MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Recent commit 16a214 to move the maxaccept parameter to listeners didn't set it on the peers' listeners, resulting in the value zero being used there. This caused a busy loop for each peers section, because no incoming connection could be accepted. Thanks to Hervé Commowick for reporting this issue. --- src/cfgparse.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/cfgparse.c b/src/cfgparse.c index c31774320..9fa188192 100644 --- a/src/cfgparse.c +++ b/src/cfgparse.c @@ -7135,6 +7135,7 @@ out_uri_auth_compat: while (*last) { curpeers = *last; if (curpeers->peers_fe) { + LIST_NEXT(&curpeers->peers_fe->conf.listeners, struct listener *, by_fe)->maxaccept = 1; last = &curpeers->next; continue; }