blocks|key|2705818|text|CLOSE_WAIT意味着您的程序仍然在运行，并且没有关闭套接字(内核正在等待它这样做)。将-p添加到netstat以获取pid，然后更有力地杀死它(如果需要的话使用SIGKILL+)。这应该可以消除您的CLOSE_WAIT套接字。您还可以使用ps查找pid。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2705819|SO_REUSEADDR用于服务器和TIME_WAIT套接字，因此这里不适用。|2705820|entityMap^0|0|A|1A|2|1F|7|2B|7|2U|A|3E|2|0|0|C|I|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$]]

<code>CLOSE_WAIT</code> means your program is still running, and hasn't closed the socket (and the kernel is waiting for it to do so). Add <code>-p</code> to <code>netstat</code> to get the pid, and then kill it more forcefully (with <code>SIGKILL</code> if needed). That should get rid of your <code>CLOSE_WAIT</code> sockets. You can also use <code>ps</code> to find the pid.

<code>SO_REUSEADDR</code> is for servers and <code>TIME_WAIT</code> sockets, so doesn't apply here.

blocks|key|2705841|text|正如克里斯特·克拉克所描述的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2705842|CLOSE_WAIT意味着连接的本地端已经从另一端接收到一个FIN，但是OS正在等待本地端的程序实际关闭其连接。
问题是在本地机器上运行的程序没有关闭套接字。这不是TCP调优问题。当程序保持连接打开时，连接可以(并且非常正确)永远停留在CLOSE_WAIT中。
一旦本地程序关闭了套接字，操作系统就可以将FIN发送到远程终端，这将使您在等待FIN的ACK时切换到LAST_ACK。一旦接收到该连接，连接就完成并从connection表中删除(如果您的端处于CLOSE_WAIT状态，则不会以TIME_WAIT状态结束)。|blockquote|2705843|entityMap|0|LINK|mutability|MUTABLE|url|http://unix.derkeiler.com/Mailing-Lists/SunManagers/2006-01/msg00367.html^0|2|8|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|C|$]]|$1|G|3|-4|5|6|7|T|8|@]|9|@]|C|$]]]|H|$I|$5|J|K|L|C|$M|N]]]]

As described by <a href="http://unix.derkeiler.com/Mailing-Lists/SunManagers/2006-01/msg00367.html" rel="noreferrer">Crist Clark</a>.

<blockquote>
 CLOSE_WAIT means that the local end of the connection has received a
 FIN from the other end, but the OS is waiting for the program at the
 local end to actually close its connection.
 
 The problem is your program running on the local machine is not
 closing the socket. It is not a TCP tuning issue. A connection can
 (and quite correctly) stay in CLOSE_WAIT forever while the program
 holds the connection open.
 
 Once the local program closes the socket, the OS can send the FIN to
 the remote end which transitions you to LAST_ACK while you wait for
 the ACK of the FIN. Once that is received, the connection is finished
 and drops from the connection table (if your end is in CLOSE_WAIT you
 do not end up in the TIME_WAIT state).
</blockquote>

blocks|key|595409|text|您可以使用ss命令强行关闭套接字；ss命令是一种工具，用于转储套接字统计信息，并以类似的方式(尽管更简单和更快)显示信息到netstat。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|595410|若要在CLOSE_WAIT状态下关闭任何套接字，请运行此套接字(以root用户身份)|595411|$+ss+--tcp+state+CLOSE-WAIT+--kill|code-block|syntax|javascript|595412|你也可以过滤你的行动。|595413|$+ss+--tcp+state+CLOSE-WAIT+'(+dport+=+22+or+dst+1.1.1.1+)'+--kill|595414|entityMap^0|5|2|H|2|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|R|$]]

You can forcibly close sockets with <code>ss</code> command; the <code>ss</code> command is a tool used to dump socket statistics and displays information in similar fashion (although simpler and faster) to netstat.
To kill any socket in CLOSE_WAIT state, run this (as root)
<pre><code>$ ss --tcp state CLOSE-WAIT --kill
</code></pre>
You may also filter your action
<pre><code>$ ss --tcp state CLOSE-WAIT '( dport = 22 or dst 1.1.1.1 )' --kill
</code></pre>

blocks|key|2705845|text|尽管太多的CLOSE_WAIT连接意味着您的第一个代码有问题，这是被接受的，不是很好的实践。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2705846|您可能需要结帐：https://github.com/rghose/kill-close-wait-connections|offset|length|2705847|此脚本所做的是发送连接等待的ACK。|2705848|这就是对我起作用的东西。|2705849|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/rghose/kill-close-wait-connections^0|0|8|1H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Even though too much of CLOSE_WAIT connections means there is something wrong with your code in the first and this is accepted not good practice.

You might want to check out: <a href="https://github.com/rghose/kill-close-wait-connections" rel="noreferrer">https://github.com/rghose/kill-close-wait-connections</a>

What this script does is send out the ACK which the connection was waiting for.

This is what worked for me.

blocks|key|595315|text|我在最新的Tomcat服务器(7.0.40)上也遇到了同样的问题。有几天没反应一次。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|595316|要查看打开的连接，可以使用：|595317|sudo+netstat+-tonp+%7C+grep+jsvc+%7C+grep+--regexp="127.0.0.1:443"+--regexp="127.0.0.1:80"+%7C+grep+CLOSE_WAIT|code-block|syntax|javascript|595318|正如在这个职位中提到的，您可以使用/proc/sys/net/ipv4/tcp_keepalive_time来查看这些值。该值以秒为单位，默认值为7200+(即2小时)。|offset|length|style|CODE|595319|要更改它们，您需要编辑/etc/sysctl.conf。|595320|Open/create+`/etc/sysctl.conf`
Add+`net.ipv4.tcp_keepalive_time+=+120`+and+save+the+file
Invoke+`sysctl+-p+/etc/sysctl.conf`
Verify+using+`cat+/proc/sys/net/ipv4/tcp_keepalive_time`|595321|entityMap|0|LINK|mutability|MUTABLE|url|https://unix.stackexchange.com/questions/10106/orphaned-connections-in-close-wait-state^0|0|0|0|H|11|3|4|0|0|B|G|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@$K|14|L|15|M|N]]|9|@$K|16|L|17|1|18]]|A|$]]|$1|O|3|P|5|6|7|19|8|@$K|1A|L|1B|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|S|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I'm also having the same issue with a very latest Tomcat server (7.0.40). It goes non-responsive once for a couple of days.

To see open connections, you may use:

<pre><code>sudo netstat -tonp | grep jsvc | grep --regexp="127.0.0.1:443" --regexp="127.0.0.1:80" | grep CLOSE_WAIT
</code></pre>

As mentioned in <a href="https://unix.stackexchange.com/questions/10106/orphaned-connections-in-close-wait-state">this post</a>, you may use <code>/proc/sys/net/ipv4/tcp_keepalive_time</code> to view the values. The value seems to be in seconds and defaults to 7200 (i.e. 2 hours).

To change them, you need to edit <code>/etc/sysctl.conf</code>.

<pre><code>Open/create `/etc/sysctl.conf`
Add `net.ipv4.tcp_keepalive_time = 120` and save the file
Invoke `sysctl -p /etc/sysctl.conf`
Verify using `cat /proc/sys/net/ipv4/tcp_keepalive_time`
</code></pre>

blocks|key|2705856|text|应该指出，客户机和服务器端的Socket实例都需要显式调用close()。如果只有一个端点调用close()，那么套接字将保持CLOSE_WAIT状态。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2705857|entityMap^0|E|6|T|7|1B|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

It should be mentioned that the <code>Socket</code> instance in both client and the server end needs to explicitly invoke <code>close()</code>. If only one of the ends invokes <code>close()</code> then too, the socket will remain in CLOSE_WAIT state.

blocks|key|595378|text|还值得注意的是，如果您的程序生成了一个新进程，该进程可能继承您打开的所有句柄。即使在您自己的程序closs之后，这些继承的句柄仍然可以通过孤立的子进程存活。而且它们在netstat中的表现也不一定完全相同。但是，尽管如此，当这个子进程还活着时，套接字将在CLOSE_WAIT中挂起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|595379|我有个案子是我负责亚行的。如果还没有运行，亚行本身就会产生一个服务器进程。这最初继承了我所有的句柄，但在我进行调查时并没有显示出拥有它们(+macOS和Windows都是如此--对Linux不太确定)。|595380|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It is also worth noting that if your program spawns a new process, that process may inherit all your opened handles. Even after your own program closs, those inherited handles can still be alive via the orphaned child process. And they don't necessarily show up quite the same in netstat. But all the same, the socket will hang around in CLOSE_WAIT while this child process is alive.

I had a case where I was running ADB. ADB itself spawns a server process if its not already running. This inherited all my handles initially, but did not show up as owning any of them when I was investigating (the same was true for both macOS and Windows - not sure about Linux).

I have written a small program that interacts with a server on a specific port. The program works fine, but:

Once the program terminated unexpectedly, and ever since that socket connection is shown in <code>CLOSE_WAIT</code> state. If I try to run a program it hangs and I have to force it close, which accumulates even more <code>CLOSE_WAIT</code> socket connections.

Is there a way to flush these connections?

How do I remove a CLOSE_WAIT socket connection

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我已经编写了一个与特定端口上的服务器交互的小程序。该程序运行良好，但：一旦程序意外地终止，并且从此套接字连接以CLOSE_WAIT状态显示。如果我试图运行一个程序，它会挂起，我不得不强制关闭它，这会积累更多的CLOSE_WAIT套接字连接。有办法冲洗这些连接吗？

问如何删除CLOSE_WAIT套接字连接
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何删除CLOSE_WAIT套接字连接EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何删除CLOSE_WAIT套接字连接
EN