<blockquote>
<p>I have see similar behavior on CentOS with default network initialization subsystem.<br>
After I reconfigured to use <code>systemd-networkd</code> instead default network initialization, then i not see more "CLOSE_WAIT".</p>
<p>Could you reconfigure network using <code>systemd-networkd</code> and then retest.</p>
</blockquote>
<p>Hey sergey, i could try this too. But as far as I understand it. CLOSE_WAIT is a issue by the application, not finally closing the session.</p>
<p>As described by <a href="http://unix.derkeiler.com/Mailing-Lists/SunManagers/2006-01/msg00367.html" rel="nofollow">Crist Clark</a></p>
<blockquote>
<p>CLOSE_WAIT means that the local end of the connection has received<br>
a FIN from the other end, but the OS is waiting for the program at the<br>
local end to actually close its connection.</p>
<p>The problem is your program running on the local machine is not closing<br>
the socket. It is not a TCP tuning issue. A connection can (and quite<br>
correctly) stay in CLOSE_WAIT forever while the program holds the<br>
connection open.</p>
</blockquote>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/1881#issuecomment-469699091">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36ZWGBp0kZpG1QIWaXUS7YhlOgIoFGks5vTn6egaJpZM4bePkf">mute the thread</a>.<img src="https://github.com/notifications/beacon/AF36Ze_r_hILK2QV0Uj37wjb-TT8P0JCks5vTn6egaJpZM4bePkf.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@kvrban in #1881: \u003e I have see similar behavior on CentOS with default network initialization subsystem.\r\n\u003e After I reconfigured to use `systemd-networkd` instead default network initialization, then i not see more \"CLOSE_WAIT\".\r\n\u003e \r\n\u003e Could you reconfigure network using `systemd-networkd` and then retest.\r\n\r\nHey sergey, i could try this too. But as far as I understand it. CLOSE_WAIT is a issue by the application, not finally closing the session. \r\n\r\nAs described by [Crist Clark](http://unix.derkeiler.com/Mailing-Lists/SunManagers/2006-01/msg00367.html)\r\n\r\n\u003e CLOSE_WAIT means that the local end of the connection has received\r\n\u003e a FIN from the other end, but the OS is waiting for the program at the\r\n\u003e local end to actually close its connection.\r\n\u003e \r\n\u003e The problem is your program running on the local machine is not closing\r\n\u003e the socket. It is not a TCP tuning issue. A connection can (and quite\r\n\u003e correctly) stay in CLOSE_WAIT forever while the program holds the\r\n\u003e connection open."}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/1881#issuecomment-469699091"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/kamailio/kamailio/issues/1881#issuecomment-469699091",
"url": "https://github.com/kamailio/kamailio/issues/1881#issuecomment-469699091",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>