<?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 Forwarder Port 9996 has intermittent connectivity issues since upgrading indexers to Splunk 4.3.2 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51426#M9863</link>
    <description>&lt;P&gt;For some reason, ever since upgrading from 4.3.1 to 4.3.2, my 2 indexers have been experiencing intermittent connectivity issues with the default Forwarder Port TCP 9996.&lt;/P&gt;

&lt;P&gt;They are taking turns doing this and I am afraid this can affect my client forwarder traffic down the line. &lt;/P&gt;

&lt;P&gt;Anyone else having this problem. &lt;/P&gt;

&lt;P&gt;I submitted a case to Splunk about this but wondering is anyone else is having this problem. &lt;/P&gt;

&lt;P&gt;I know for sure this has never happened before and this started happening when I upgraded to 4.3.2&lt;/P&gt;

&lt;P&gt;Let me know if theres anything I should do or look at to determine the issue. &lt;/P&gt;

&lt;P&gt;Thanks. &lt;/P&gt;

&lt;P&gt;Brian&lt;/P&gt;</description>
    <pubDate>Mon, 14 May 2012 18:38:06 GMT</pubDate>
    <dc:creator>balbano</dc:creator>
    <dc:date>2012-05-14T18:38:06Z</dc:date>
    <item>
      <title>Forwarder Port 9996 has intermittent connectivity issues since upgrading indexers to Splunk 4.3.2</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51426#M9863</link>
      <description>&lt;P&gt;For some reason, ever since upgrading from 4.3.1 to 4.3.2, my 2 indexers have been experiencing intermittent connectivity issues with the default Forwarder Port TCP 9996.&lt;/P&gt;

&lt;P&gt;They are taking turns doing this and I am afraid this can affect my client forwarder traffic down the line. &lt;/P&gt;

&lt;P&gt;Anyone else having this problem. &lt;/P&gt;

&lt;P&gt;I submitted a case to Splunk about this but wondering is anyone else is having this problem. &lt;/P&gt;

&lt;P&gt;I know for sure this has never happened before and this started happening when I upgraded to 4.3.2&lt;/P&gt;

&lt;P&gt;Let me know if theres anything I should do or look at to determine the issue. &lt;/P&gt;

&lt;P&gt;Thanks. &lt;/P&gt;

&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2012 18:38:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51426#M9863</guid>
      <dc:creator>balbano</dc:creator>
      <dc:date>2012-05-14T18:38:06Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Port 9996 has intermittent connectivity issues since upgrading indexers to Splunk 4.3.2</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51427#M9864</link>
      <description>&lt;P&gt;Is there no one having this issue?&lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2012 14:20:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51427#M9864</guid>
      <dc:creator>balbano</dc:creator>
      <dc:date>2012-05-18T14:20:19Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Port 9996 has intermittent connectivity issues since upgrading indexers to Splunk 4.3.2</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51428#M9865</link>
      <description>&lt;P&gt;My issue was due to the indexers being overloaded due to failed time parsing. &lt;/P&gt;

&lt;P&gt;I have corrected this and the performance has much improved. &lt;/P&gt;

&lt;P&gt;I still think there is something different in the way that Splunk handled time parsing prior to 4.3.2 since I have never experienced these connection issues but Splunk Support helped me isolate the issue. &lt;/P&gt;

&lt;P&gt;Thanks. &lt;BR /&gt;
B&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jul 2012 14:31:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51428#M9865</guid>
      <dc:creator>balbano</dc:creator>
      <dc:date>2012-07-06T14:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Port 9996 has intermittent connectivity issues since upgrading indexers to Splunk 4.3.2</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51429#M9866</link>
      <description>&lt;P&gt;Can you explain how did you do it?? because i'll experiencing this last week till now..&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2013 02:55:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51429#M9866</guid>
      <dc:creator>christantoy</dc:creator>
      <dc:date>2013-05-28T02:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Port 9996 has intermittent connectivity issues since upgrading indexers to Splunk 4.3.2</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51430#M9867</link>
      <description>&lt;P&gt;Please share what you've done to resolve the issue. Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2017 04:12:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Port-9996-has-intermittent-connectivity-issues-since/m-p/51430#M9867</guid>
      <dc:creator>dantimola</dc:creator>
      <dc:date>2017-07-14T04:12:48Z</dc:date>
    </item>
  </channel>
</rss>

