<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic resolving a close_wait status on a particular port in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740183#M21998</link>
    <description>Hi there -- &lt;BR /&gt;&lt;BR /&gt;I have a server running Red Hat 7.3 and there is a CLOSE_WAIT status on a particular port that is preventing my starting a program that needs that port available. Is there a way, other than restarting the server, of resolving the CLOSE_WAIT status on the port? Thanks.</description>
    <pubDate>Mon, 27 Feb 2006 12:33:45 GMT</pubDate>
    <dc:creator>Andrew Kaplan</dc:creator>
    <dc:date>2006-02-27T12:33:45Z</dc:date>
    <item>
      <title>resolving a close_wait status on a particular port</title>
      <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740183#M21998</link>
      <description>Hi there -- &lt;BR /&gt;&lt;BR /&gt;I have a server running Red Hat 7.3 and there is a CLOSE_WAIT status on a particular port that is preventing my starting a program that needs that port available. Is there a way, other than restarting the server, of resolving the CLOSE_WAIT status on the port? Thanks.</description>
      <pubDate>Mon, 27 Feb 2006 12:33:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740183#M21998</guid>
      <dc:creator>Andrew Kaplan</dc:creator>
      <dc:date>2006-02-27T12:33:45Z</dc:date>
    </item>
    <item>
      <title>Re: resolving a close_wait status on a particular port</title>
      <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740184#M21999</link>
      <description>netstat -nap | grep CLOSE_WAIT&lt;BR /&gt;&lt;BR /&gt;Run this as 'root'.  Does this list a PID?</description>
      <pubDate>Mon, 27 Feb 2006 15:03:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740184#M21999</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2006-02-27T15:03:33Z</dc:date>
    </item>
    <item>
      <title>Re: resolving a close_wait status on a particular port</title>
      <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740185#M22000</link>
      <description>It appears the pid is 29877. I am referring to the column after the CLOSE_WAIT entry which reads 29877/df.</description>
      <pubDate>Mon, 27 Feb 2006 15:13:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740185#M22000</guid>
      <dc:creator>Andrew Kaplan</dc:creator>
      <dc:date>2006-02-27T15:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: resolving a close_wait status on a particular port</title>
      <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740186#M22001</link>
      <description>After killing the process try a "service network" restart as this may refresh the port.</description>
      <pubDate>Tue, 28 Feb 2006 02:10:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740186#M22001</guid>
      <dc:creator>Andrew Cowan</dc:creator>
      <dc:date>2006-02-28T02:10:59Z</dc:date>
    </item>
    <item>
      <title>Re: resolving a close_wait status on a particular port</title>
      <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740187#M22002</link>
      <description>CLOSE_WAIT means that the system is waiting for the local process to close &lt;BR /&gt;the socket. The socket doesn't get closed until all the processes that have descriptors for it call close() (or terminate, since that automatically closes all of a process's descriptors). &lt;BR /&gt;&lt;BR /&gt;So you need only to close your program which use a open socket in a listening mode.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sergejs&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Feb 2006 03:23:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740187#M22002</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2006-02-28T03:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: resolving a close_wait status on a particular port</title>
      <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740188#M22003</link>
      <description>I tried to kill the process using the kill -9 syntax as root, but it did not seem to have any effect. Despite that, I ran the service network restart command and while that went by without a problem, the CLOSE_WAIT status of port did not change. &lt;BR /&gt;&lt;BR /&gt;I ran the ps -ef command and grepped for the application, but there was no listing of it.</description>
      <pubDate>Tue, 28 Feb 2006 08:32:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740188#M22003</guid>
      <dc:creator>Andrew Kaplan</dc:creator>
      <dc:date>2006-02-28T08:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: resolving a close_wait status on a particular port</title>
      <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740189#M22004</link>
      <description>If the process refuses to die, try killing the parent.</description>
      <pubDate>Tue, 28 Feb 2006 09:56:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740189#M22004</guid>
      <dc:creator>Andrew Cowan</dc:creator>
      <dc:date>2006-02-28T09:56:08Z</dc:date>
    </item>
    <item>
      <title>Re: resolving a close_wait status on a particular port</title>
      <link>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740190#M22005</link>
      <description>Try lsof -i TCP |grep [port# | or named port defined in /etc/services] then kill the associated pid of that process.  If this works it could then be incorporated into a script.</description>
      <pubDate>Thu, 02 Mar 2006 15:10:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/resolving-a-close-wait-status-on-a-particular-port/m-p/3740190#M22005</guid>
      <dc:creator>Tucker_1</dc:creator>
      <dc:date>2006-03-02T15:10:33Z</dc:date>
    </item>
  </channel>
</rss>

