<?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 Communication failing between forwarder and receiver in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94092#M19583</link>
    <description>&lt;P&gt;My new forwarder appears not to be talking to the configured indexer(s)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout]
defaultGroup = splunk1_9997_splunk2_9997
disabled = false
indexAndForward = 0

[tcpout:splunk1_9997_splunk2_9997]
autoLB = true
server = splunk1:9997,splunk2:9997
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have another forwarder with an identical outputs.conf and that works fine. &lt;/P&gt;

&lt;P&gt;Inputs.conf on the indexers looks like:&lt;BR /&gt;
[splunktcp://10.1.2.1:9997]&lt;/P&gt;

&lt;P&gt;On the forwarder&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;03-16-2012 14:20:24.902 +1000 INFO  TcpOutputProc - Connected to idx=10.1.2.3:9997
03-16-2012 14:20:24.902 +1000 INFO  TcpOutputProc - Connection to 10.1.2.3:9997 closed. Connection closed by server.
03-16-2012 14:20:24.903 +1000 WARN  TcpOutputProc - Applying quarantine to idx=10.1.2.3:9997 numberOfFailures=2
03-16-2012 14:20:24.903 +1000 INFO  TcpOutputProc - Connected to idx=10.1.2.3:9997
03-16-2012 14:20:24.904 +1000 INFO  TcpOutputProc - Connection to 10.1.2.3:9997 closed. Connection closed by server.
03-16-2012 14:20:24.904 +1000 WARN  TcpOutputProc - Applying quarantine to idx=10.1.2.3:9997 numberOfFailures=3
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;On the indexer&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;03-16-2012 14:20:24.903 +1000 INFO  TcpInputProc - No matching config for 10.1.2.4
03-16-2012 14:20:24.903 +1000 WARN  TcpInputProc - Could not find matching host.
03-16-2012 14:20:24.903 +1000 INFO  TcpInputProc - No matching config for 10.1.2.4
03-16-2012 14:20:24.903 +1000 WARN  TcpInputProc - Could not find matching host.
03-16-2012 14:20:24.904 +1000 INFO  TcpInputProc - No matching config for 10.1.2.4
03-16-2012 14:20:24.904 +1000 WARN  TcpInputProc - Could not find matching host.
03-16-2012 14:20:24.904 +1000 INFO  TcpInputProc - No matching config for 10.1.2.4
03-16-2012 14:20:24.904 +1000 WARN  TcpInputProc - Could not find matching host.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What matching config is it looking for? Connectivity is definitely fine. &lt;/P&gt;

&lt;P&gt;&lt;B&gt;Updated&lt;/B&gt; Corrected inputs.conf to outputs.conf, added indexer inputs.conf as per Kristian's comment&lt;/P&gt;</description>
    <pubDate>Fri, 16 Mar 2012 04:28:53 GMT</pubDate>
    <dc:creator>willthames2</dc:creator>
    <dc:date>2012-03-16T04:28:53Z</dc:date>
    <item>
      <title>Communication failing between forwarder and receiver</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94092#M19583</link>
      <description>&lt;P&gt;My new forwarder appears not to be talking to the configured indexer(s)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout]
defaultGroup = splunk1_9997_splunk2_9997
disabled = false
indexAndForward = 0

[tcpout:splunk1_9997_splunk2_9997]
autoLB = true
server = splunk1:9997,splunk2:9997
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have another forwarder with an identical outputs.conf and that works fine. &lt;/P&gt;

&lt;P&gt;Inputs.conf on the indexers looks like:&lt;BR /&gt;
[splunktcp://10.1.2.1:9997]&lt;/P&gt;

&lt;P&gt;On the forwarder&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;03-16-2012 14:20:24.902 +1000 INFO  TcpOutputProc - Connected to idx=10.1.2.3:9997
03-16-2012 14:20:24.902 +1000 INFO  TcpOutputProc - Connection to 10.1.2.3:9997 closed. Connection closed by server.
03-16-2012 14:20:24.903 +1000 WARN  TcpOutputProc - Applying quarantine to idx=10.1.2.3:9997 numberOfFailures=2
03-16-2012 14:20:24.903 +1000 INFO  TcpOutputProc - Connected to idx=10.1.2.3:9997
03-16-2012 14:20:24.904 +1000 INFO  TcpOutputProc - Connection to 10.1.2.3:9997 closed. Connection closed by server.
03-16-2012 14:20:24.904 +1000 WARN  TcpOutputProc - Applying quarantine to idx=10.1.2.3:9997 numberOfFailures=3
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;On the indexer&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;03-16-2012 14:20:24.903 +1000 INFO  TcpInputProc - No matching config for 10.1.2.4
03-16-2012 14:20:24.903 +1000 WARN  TcpInputProc - Could not find matching host.
03-16-2012 14:20:24.903 +1000 INFO  TcpInputProc - No matching config for 10.1.2.4
03-16-2012 14:20:24.903 +1000 WARN  TcpInputProc - Could not find matching host.
03-16-2012 14:20:24.904 +1000 INFO  TcpInputProc - No matching config for 10.1.2.4
03-16-2012 14:20:24.904 +1000 WARN  TcpInputProc - Could not find matching host.
03-16-2012 14:20:24.904 +1000 INFO  TcpInputProc - No matching config for 10.1.2.4
03-16-2012 14:20:24.904 +1000 WARN  TcpInputProc - Could not find matching host.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What matching config is it looking for? Connectivity is definitely fine. &lt;/P&gt;

&lt;P&gt;&lt;B&gt;Updated&lt;/B&gt; Corrected inputs.conf to outputs.conf, added indexer inputs.conf as per Kristian's comment&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2012 04:28:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94092#M19583</guid>
      <dc:creator>willthames2</dc:creator>
      <dc:date>2012-03-16T04:28:53Z</dc:date>
    </item>
    <item>
      <title>Re: Communication failing between forwarder and receiver</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94093#M19584</link>
      <description>&lt;P&gt;Could you please post the inputs.conf files for the indexers. &lt;/P&gt;

&lt;P&gt;Also, you said that other forwarders had the same INPUTS.CONF, but surely you mean OUTPUTS.CONF, right?&lt;/P&gt;

&lt;P&gt;/k&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2012 09:57:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94093#M19584</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-03-16T09:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: Communication failing between forwarder and receiver</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94094#M19585</link>
      <description>&lt;P&gt;I was misunderstanding the [splunktcp://ipaddress:port] configuration.&lt;BR /&gt;
I thought the ipaddress was localhost, but it's actually remoteserver (forwarders that are allowed to connect). &lt;/P&gt;

&lt;P&gt;Adding the new forwarders to inputs.conf fixes this issue. Thanks to Kristian for helping me look in the right direction. &lt;/P&gt;</description>
      <pubDate>Sun, 18 Mar 2012 23:16:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94094#M19585</guid>
      <dc:creator>willthames2</dc:creator>
      <dc:date>2012-03-18T23:16:21Z</dc:date>
    </item>
    <item>
      <title>Re: Communication failing between forwarder and receiver</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94095#M19586</link>
      <description>&lt;P&gt;you're welcome. /K&lt;/P&gt;</description>
      <pubDate>Mon, 19 Mar 2012 10:31:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Communication-failing-between-forwarder-and-receiver/m-p/94095#M19586</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-03-19T10:31:56Z</dc:date>
    </item>
  </channel>
</rss>

