[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 Bug 61499 depends on bug 63010, which changed state. Bug 63010 Summary: mod_proxy_hcheck when health checks configured, esp. vs down service, consumes large memory https://bz.apache.org/bugzilla/show_bug.cgi?id=63010 What

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 Christophe JAILLET changed: What|Removed |Added Depends on||63010 Status|NEW

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 AK changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #9 from AK --- Memory

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 --- Comment #8 from Graham Leggett --- Backported to 2.4.35. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail:

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 Jim Jagielski changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #7 from Jim

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 --- Comment #6 from AK --- Hi, I have just patched version 2.4.34 (removed the line) and TCP health check started to work. But httpd process is still consuming more and more memory. In approx. 20 hours it rised in heap up to 20GB. I have 260

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 --- Comment #5 from Jim Jagielski --- Yes, it does not do the double-set for HTTP so this is likely fluff left over from the rework around 2.4.27. Thx for the patch -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 --- Comment #4 from Dominik Stillhard --- the line i was talking about: https://github.com/apache/httpd/blob/5bd8f20a5063f47e93fe148032ec8ffa5d04a12e/modules/proxy/mod_proxy_hcheck.c#L615 ;) -- You are receiving this mail because: You are

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 --- Comment #3 from Dominik Stillhard --- I tested this in version 2.3.34 and the bug still exists. The problem is, that compare to http checks, in the function ap_proxy_connect_backend (proxy_util.c) the backend_addr is NULL. Thats why

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 --- Comment #2 from Dominik Stillhard --- Created attachment 36143 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36143=edit patch removing the line, based on trunk -- You are receiving this mail because: You are the assignee for

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 cbarb...@okta.com changed: What|Removed |Added CC||cbarb...@okta.com -- You are

[Bug 61499] TCP healthchecks failing falsely / not actually checking

https://bz.apache.org/bugzilla/show_bug.cgi?id=61499 --- Comment #1 from Luca Toscano --- Hi, it might be due to https://github.com/apache/httpd/commit/77ebb516535eecd90b458c52647b08a4da82e84e Any chance that you could try the 'no-proxy' variable via SetEnvIf? -- You