| Summary: | proxy connections to target left in CLOSE_WAIT state | ||
|---|---|---|---|
| Product: | Apache httpd-2 | Reporter: | Lothar <lothar.webmin> |
| Component: | mod_proxy | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | tech |
| Priority: | P2 | ||
| Version: | 2.4.51 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Attachments: | Trace8 Log filtered by one PID, serving the Request IP-Addresses/hostnames anonymised ( | ||
pstack 27036 #0 0x00007f4e0ac060c3 in __epoll_wait_nocancel () from /lib64/libc.so.6 #1 0x00007f4e0b758a59 in ?? () #2 0x00007ffcdd3b13fc in ?? () #3 0x00007ffcdd3b14a4 in ?? () #4 0x00007ffcdd3b14a8 in ?? () #5 0x0000000001bb9b98 in ?? () #6 0x0000000001bb9cd8 in ?? () #7 0x0000000001bb9b80 in ?? () #8 0xffffffffffffffff in ?? () #9 0x00007ffcdd3b14a4 in ?? () #10 0x0000000001bb9ca8 in ?? () #11 0x0000000001bb9cd8 in ?? () #12 0x00007ffcdd3b14a8 in ?? () #13 0x00007f4e092b1721 in ?? () #14 0x0000000001b99a98 in ?? () #15 0x0000000001bace78 in ?? () #16 0x0000000001b994c0 in ?? () #17 0x00007ffcdd3b1540 in ?? () #18 0x0000000001bb9cd8 in ?? () #19 0x00007f4e0b753283 in ?? () #20 0x0000000001bb7e20 in ?? () #21 0x0000000001b994c0 in ?? () #22 0x0000000001bb9ca0 in ?? () #23 0x0000000001bb9b80 in ?? () #24 0x0000000001bb9b38 in ?? () #25 0xffffffffffffffff in ?? () #26 0x00007ffcdd3b14a4 in ?? () #27 0x00007ffcdd3b14a8 in ?? () #28 0x0000000001b99040 in ?? () #29 0x0000000001bb9c40 in ?? () #30 0x0000000001b99040 in ?? () #31 0x0000000001bb9af8 in ?? () #32 0x0000000001b994c0 in ?? () #33 0x0000000001b99040 in ?? () #34 0x00007ffcdd3b15b0 in ?? () #35 0x0000000001bb7e20 in ?? () #36 0x0000000000440910 in ?? () at util_filter.c:593 #37 0x00007f4e09094f35 in ?? () #38 0x0000000001b7bc68 in ?? () #39 0x00007f4e0b7477d7 in ?? () #40 0x0000000000000000 in ?? () (In reply to Piotr Staszeski from comment #1) > pstack 27036 missclick - @Lothar do You also see related FIN_WAIT2 connections? Maybe You observe same issues as I in Bug 65662 (In reply to Lothar from comment #0) > Also the behavior has changed, with apache 2.4.46 the connection was closed > smoothly: > apache -> target ACK > target -> apache FIN,ACK > apache -> target ACK > apache -> target FIN,ACK > > With apache 2.4.51 the last FIN,ACK is not sent anymore but we receive > target -> apache RST, ACK after 10 sec. What happens to the connection on the client side when the target/backend server initiates connection close like the above? Let's track this at a single place (bug 65662) since the reports look very similar. *** This bug has been marked as a duplicate of bug 65662 *** Created attachment 38100 [details]
Trace8 Log filtered by one PID, serving the Request IP-Addresses/hostnames anonymised (
Trace8 Log filtered by one PID, which was serving the Request
IP-Addresses/hostnames anonymised
(In reply to Piotr Staszeski from comment #2) > (In reply to Piotr Staszeski from comment #1) > > pstack 27036 > > missclick - @Lothar do You also see related FIN_WAIT2 connections? Maybe You > observe same issues as I in Bug 65662 The Connection switches immediately from ESTABLISHED into CLOSE_WAIT state (In reply to Yann Ylavic from comment #3) > (In reply to Lothar from comment #0) > > Also the behavior has changed, with apache 2.4.46 the connection was closed > > smoothly: > > apache -> target ACK > > target -> apache FIN,ACK > > apache -> target ACK > > apache -> target FIN,ACK > > > > With apache 2.4.51 the last FIN,ACK is not sent anymore but we receive > > target -> apache RST, ACK after 10 sec. > > What happens to the connection on the client side when the target/backend > server initiates connection close like the above? The Client receives a 200 OK and everything on client side is OK *** This bug has been marked as a duplicate of bug 65662 *** Backported to v2.4.52. |
Hi all, since we updated apache from 2.4.46 to 2.4.51 we have a lot of open connections to destination hanging in "CLOSE_WAIT" state. The connection is closed by target after a 10 secs. with a TCP RST. Which causes alerts in our monitoring system. I tried to disable keepalive with SetEnv proxy-nokeepalive 1 We are using this config: <IfModule mod_proxy.c> ProxyRequests On AllowCONNECT 443 SetEnv proxy-nokeepalive 1 <Proxy "*"> Require all granted </Proxy> </IfModule> The Client is initiation a connection via method CONNECT: CONNECT www.example.com:443 HTTP/1.1 Somehow disable keepalive is not working. Also the behavior has changed, with apache 2.4.46 the connection was closed smoothly: apache -> target ACK target -> apache FIN,ACK apache -> target ACK apache -> target FIN,ACK With apache 2.4.51 the last FIN,ACK is not sent anymore but we receive target -> apache RST, ACK after 10 sec. Could this be fixed, or is there any workaround ( like disable keepalive) Thanks a lot! Kind Regards, Lothar