<?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 Re: Connection errors to heavy forwarders in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173084#M34812</link>
    <description>&lt;P&gt;issue was with the ESX server hosting the HF - very high iowait was the issue&lt;/P&gt;</description>
    <pubDate>Wed, 23 Mar 2016 00:46:12 GMT</pubDate>
    <dc:creator>ebaileytu</dc:creator>
    <dc:date>2016-03-23T00:46:12Z</dc:date>
    <item>
      <title>Connection errors to heavy forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173081#M34809</link>
      <description>&lt;P&gt;we have the following setup&lt;/P&gt;

&lt;P&gt;2 heavy forwarders (HF) forwarding data to 4 indexers&lt;/P&gt;

&lt;P&gt;We just added another 100 Universal forwarders (UF) to the environment so now we have about 800 UFs connecting to the HFs. I am starting to see a troubling number of connection error messages (about 7000 per hour) from the UFs such as:&lt;/P&gt;

&lt;P&gt;05-20-2014 21:10:16.949 -0500 ERROR TcpOutputFd - Connection to host=xx.xxx.xx.xx:xxxx failed. sock_error = 10054. SSL Error = error:00000000:lib(0):func(0):reason(0)&lt;/P&gt;

&lt;P&gt;(We are using SSL for connections from the UF to HF)&lt;/P&gt;

&lt;P&gt;and&lt;/P&gt;

&lt;P&gt;05-20-2014 21:09:59.394 -0500 ERROR TcpOutputFd - Connection to host=xx.xxx.xx.xx:xxxx failed&lt;/P&gt;

&lt;P&gt;Data is getting forwarded from the UF to the HF but from tests I can see some data is delayed. Do the errors indicate I need to adjust a setting or just deploy another HF? I do not see high resource utilization on the HF.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 21 May 2014 02:35:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173081#M34809</guid>
      <dc:creator>ebaileytu</dc:creator>
      <dc:date>2014-05-21T02:35:33Z</dc:date>
    </item>
    <item>
      <title>Re: Connection errors to heavy forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173082#M34810</link>
      <description>&lt;P&gt;Hi, what was the solution? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 22 Mar 2016 20:33:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173082#M34810</guid>
      <dc:creator>gsopko</dc:creator>
      <dc:date>2016-03-22T20:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Connection errors to heavy forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173083#M34811</link>
      <description>&lt;P&gt;issue with ESX server storage - high iowait created chaos&lt;/P&gt;</description>
      <pubDate>Wed, 23 Mar 2016 00:45:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173083#M34811</guid>
      <dc:creator>ebaileytu</dc:creator>
      <dc:date>2016-03-23T00:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: Connection errors to heavy forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173084#M34812</link>
      <description>&lt;P&gt;issue was with the ESX server hosting the HF - very high iowait was the issue&lt;/P&gt;</description>
      <pubDate>Wed, 23 Mar 2016 00:46:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Connection-errors-to-heavy-forwarders/m-p/173084#M34812</guid>
      <dc:creator>ebaileytu</dc:creator>
      <dc:date>2016-03-23T00:46:12Z</dc:date>
    </item>
  </channel>
</rss>

