<?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 Why am I getting timeout issues from Splunk forwarders to the intermediate heavy forwarder? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-am-I-getting-timeout-issues-from-Splunk-forwarders-to-the/m-p/229519#M44663</link>
    <description>&lt;P&gt;I have a random time out issue from Splunk forwarders to the Splunk intermediate (heavy) forwarder.  &lt;/P&gt;

&lt;P&gt;When I do &lt;CODE&gt;netstat -al | grep 9997&lt;/CODE&gt;, I get:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunkndx-9997 SYN_SENT
splunkndx-9997 FIN_WAIT1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;from universal forwarder side splunkd.log &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;08-16-2016 02:08:50.047 +0000 WARN  TcpOutputProc - Forwarding to indexer group sid_9997 blocked for 1600 seconds.
08-16-2016 02:08:50.978 +0000 WARN  TcpOutputProc - Cooked connection to ip=*.*.*.*:9997 timed out
08-16-2016 02:09:11.981 +0000 WARN  TcpOutputProc - Cooked connection to ip=*.*.*.*:9997 timed out
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When I do Telnet, 9 times out of 10, I get a timeout. Is there any config I can tune up or the heavy forwarders need to be resized? The CPU usage is less than 10%. Any suggestions?&lt;/P&gt;</description>
    <pubDate>Mon, 15 Aug 2016 22:26:36 GMT</pubDate>
    <dc:creator>raindrop18</dc:creator>
    <dc:date>2016-08-15T22:26:36Z</dc:date>
    <item>
      <title>Why am I getting timeout issues from Splunk forwarders to the intermediate heavy forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-am-I-getting-timeout-issues-from-Splunk-forwarders-to-the/m-p/229519#M44663</link>
      <description>&lt;P&gt;I have a random time out issue from Splunk forwarders to the Splunk intermediate (heavy) forwarder.  &lt;/P&gt;

&lt;P&gt;When I do &lt;CODE&gt;netstat -al | grep 9997&lt;/CODE&gt;, I get:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunkndx-9997 SYN_SENT
splunkndx-9997 FIN_WAIT1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;from universal forwarder side splunkd.log &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;08-16-2016 02:08:50.047 +0000 WARN  TcpOutputProc - Forwarding to indexer group sid_9997 blocked for 1600 seconds.
08-16-2016 02:08:50.978 +0000 WARN  TcpOutputProc - Cooked connection to ip=*.*.*.*:9997 timed out
08-16-2016 02:09:11.981 +0000 WARN  TcpOutputProc - Cooked connection to ip=*.*.*.*:9997 timed out
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When I do Telnet, 9 times out of 10, I get a timeout. Is there any config I can tune up or the heavy forwarders need to be resized? The CPU usage is less than 10%. Any suggestions?&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2016 22:26:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-am-I-getting-timeout-issues-from-Splunk-forwarders-to-the/m-p/229519#M44663</guid>
      <dc:creator>raindrop18</dc:creator>
      <dc:date>2016-08-15T22:26:36Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting timeout issues from Splunk forwarders to the intermediate heavy forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-am-I-getting-timeout-issues-from-Splunk-forwarders-to-the/m-p/229520#M44664</link>
      <description>&lt;P&gt;This seems to be problem with routing taken to reach the forwarder  rather than Splunk or CPU usage. Can you verify entries in routing table? &lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2016 05:23:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-am-I-getting-timeout-issues-from-Splunk-forwarders-to-the/m-p/229520#M44664</guid>
      <dc:creator>hardikJsheth</dc:creator>
      <dc:date>2016-08-16T05:23:52Z</dc:date>
    </item>
  </channel>
</rss>

