<?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: Linux Blocking Event Forwarding in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Linux-Blocking-Event-Forwarding/m-p/371595#M67451</link>
    <description>&lt;P&gt;The log complaining about not reaching the indexer group is from the forwarder?&lt;/P&gt;

&lt;P&gt;Can you connect to the one of the indexers from the forwarder manually?  You can use openssl to try it, if it can connect just use ctrl+c to break out of it.  Don't worry if it mentions ssl handshake failures, this is just to make sure the indexer port is accessible from the forwarder.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;openssl s_client -connect {indexer_ip}:9997
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 10 May 2017 20:50:26 GMT</pubDate>
    <dc:creator>wenthold</dc:creator>
    <dc:date>2017-05-10T20:50:26Z</dc:date>
    <item>
      <title>Linux Blocking Event Forwarding</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Linux-Blocking-Event-Forwarding/m-p/371594#M67450</link>
      <description>&lt;P&gt;It's always something! &lt;/P&gt;

&lt;P&gt;Now my Linux forwarder is saying the following: &lt;/P&gt;

&lt;P&gt;05-10-2017 09:11:02.584 -0400 WARN  TcpOutputProc - Forwarding to indexer group splunk1 blocked for 87500 seconds.&lt;BR /&gt;
05-10-2017 09:12:42.594 -0400 WARN  TcpOutputProc - Forwarding to indexer group splunk1 blocked for 87600 seconds.&lt;BR /&gt;
05-10-2017 09:14:22.605 -0400 WARN  TcpOutputProc - Forwarding to indexer group splunk1 blocked for 87700 seconds.&lt;/P&gt;

&lt;P&gt;I checked to ensure that there was no outputs.conf file on the indexer (we only have 1)  which would cause a loop. &lt;/P&gt;

&lt;P&gt;I am so lost.  Any other ideas?&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 13:30:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Linux-Blocking-Event-Forwarding/m-p/371594#M67450</guid>
      <dc:creator>heats</dc:creator>
      <dc:date>2017-05-10T13:30:20Z</dc:date>
    </item>
    <item>
      <title>Re: Linux Blocking Event Forwarding</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Linux-Blocking-Event-Forwarding/m-p/371595#M67451</link>
      <description>&lt;P&gt;The log complaining about not reaching the indexer group is from the forwarder?&lt;/P&gt;

&lt;P&gt;Can you connect to the one of the indexers from the forwarder manually?  You can use openssl to try it, if it can connect just use ctrl+c to break out of it.  Don't worry if it mentions ssl handshake failures, this is just to make sure the indexer port is accessible from the forwarder.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;openssl s_client -connect {indexer_ip}:9997
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 10 May 2017 20:50:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Linux-Blocking-Event-Forwarding/m-p/371595#M67451</guid>
      <dc:creator>wenthold</dc:creator>
      <dc:date>2017-05-10T20:50:26Z</dc:date>
    </item>
  </channel>
</rss>

