topic Re: Splunk PDF Server: CLOSE_WAIT and FIN_WAIT2 in Reporting https://community.splunk.com/t5/Reporting/Splunk-PDF-Server-CLOSE-WAIT-and-FIN-WAIT2/m-p/94473#M2139 <P>I can't answer why it happens but I can tell you that I am having the same issue with an indexer. I have a case open with Splunk on the matter and I am waiting on a response.</P> <P>The issue on the indexer is a little more serious because it creates so many connections it runs the box out of RAM.</P> Tue, 10 Jul 2012 15:23:51 GMT rmcdougal 2012-07-10T15:23:51Z Splunk PDF Server: CLOSE_WAIT and FIN_WAIT2 https://community.splunk.com/t5/Reporting/Splunk-PDF-Server-CLOSE-WAIT-and-FIN-WAIT2/m-p/94472#M2138 <P>Hi,</P> <P>I have installed dthe Splunk PDF Server app. Since the install I have notice it leaves a lot of the socket connection to 8089 in the CLOSE_WAIT or FIN_WAIT2 status. Can anyone tell me why this occurs?<BR /> Below is my netstat outpur:<BR /> tcp 0 0 0.0.0.0:8089 0.0.0.0:* LISTEN<BR /> tcp 0 0 10.40.26.52:9997 10.3.252.12:48089 ESTABLISHED<BR /> tcp 38 0 127.0.0.1:33143 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 38 0 127.0.0.1:33142 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 38 0 127.0.0.1:33146 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 38 0 127.0.0.1:33145 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 38 0 127.0.0.1:33144 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 38 0 127.0.0.1:41578 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 38 0 127.0.0.1:41587 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 38 0 127.0.0.1:41597 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 38 0 127.0.0.1:42098 127.0.0.1:8089 CLOSE_WAIT<BR /> tcp 0 0 127.0.0.1:8089 127.0.0.1:33146 FIN_WAIT2<BR /> tcp 0 0 127.0.0.1:8089 127.0.0.1:33145 FIN_WAIT2<BR /> tcp 0 0 127.0.0.1:8089 127.0.0.1:33144 FIN_WAIT2<BR /> tcp 0 0 127.0.0.1:8089 127.0.0.1:33143 FIN_WAIT2<BR /> tcp 0 0 127.0.0.1:8089 127.0.0.1:33142 FIN_WAIT2</P> Mon, 28 Sep 2020 12:03:07 GMT https://community.splunk.com/t5/Reporting/Splunk-PDF-Server-CLOSE-WAIT-and-FIN-WAIT2/m-p/94472#M2138 bpolen 2020-09-28T12:03:07Z Re: Splunk PDF Server: CLOSE_WAIT and FIN_WAIT2 https://community.splunk.com/t5/Reporting/Splunk-PDF-Server-CLOSE-WAIT-and-FIN-WAIT2/m-p/94473#M2139 <P>I can't answer why it happens but I can tell you that I am having the same issue with an indexer. I have a case open with Splunk on the matter and I am waiting on a response.</P> <P>The issue on the indexer is a little more serious because it creates so many connections it runs the box out of RAM.</P> Tue, 10 Jul 2012 15:23:51 GMT https://community.splunk.com/t5/Reporting/Splunk-PDF-Server-CLOSE-WAIT-and-FIN-WAIT2/m-p/94473#M2139 rmcdougal 2012-07-10T15:23:51Z