Date: Tue, 12 Jan 2021 23:30:30 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 252624] Sockets stay in CLOSING, FIN_WAIT_X and LAST_ACK indefinitely Message-ID: <bug-252624-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252624 Bug ID: 252624 Summary: Sockets stay in CLOSING, FIN_WAIT_X and LAST_ACK indefinitely Product: Base System Version: Unspecified Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: johalun@FreeBSD.org We're running head as of March 2017 on a large number of servers. Through recent expansions we have noticed a new problem where a large amount of connections are stuck in CLOSING, FIN_WAIT_1, FIN_WAIT_2 and LAST_ACK indefinitely, until the servers runs out of memory. We don't know what is causing this but it appears that clients are not terminating the TCP connections properly. In any case, these connections should have a timeout = and be cleaned up by the kernel within reasonable time. #25986 also mentions this issue and have a suggested patch that deals with = all states but CLOSING. https://www.freebsd.org/security/advisories/FreeBSD-SA-15:13.tcp.asc claims= to have solved it but it has not. In our case we don't believe it is deliberate but if someone wanted, they c= ould easily take down servers with simple attacks like this so it is a security concern. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252624-227>