<?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: Splunk forwarder config not working in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54503#M96849</link>
    <description>&lt;P&gt;yes, I added to "local" directory like../opt/splunkforwarder/etc/apps/IND1/local/inputs.conf but it didn't work&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jun 2013 12:38:41 GMT</pubDate>
    <dc:creator>amitj</dc:creator>
    <dc:date>2013-06-04T12:38:41Z</dc:date>
    <item>
      <title>Splunk forwarder config not working</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54500#M96846</link>
      <description>&lt;P&gt;since are trying to separate out splunk forwarder config ("inputs.conf") according to indexer. we defined forwarder conf like "/opt/splunkforwarder/etc/apps/IND1/inputs.conf", "/opt/splunkforwarder/etc/apps/IND2/inputs.conf"  and restarted the splunk instance. but somehow it is not working..Do I need to define "IND1" and "IND2" as an app first?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2013 11:51:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54500#M96846</guid>
      <dc:creator>amitj</dc:creator>
      <dc:date>2013-06-04T11:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk forwarder config not working</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54501#M96847</link>
      <description>&lt;P&gt;&lt;CODE&gt;inputs.conf&lt;/CODE&gt;, like all other configuration files, need to be either in an app's &lt;CODE&gt;default&lt;/CODE&gt; directory or its &lt;CODE&gt;local&lt;/CODE&gt; directory. So, &lt;CODE&gt;/opt/splunkforwarder/etc/apps/IND1/default/inputs.conf&lt;/CODE&gt; would work, for instance.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2013 12:00:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54501#M96847</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-06-04T12:00:02Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk forwarder config not working</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54502#M96848</link>
      <description>&lt;P&gt;yes, I added to "local" directory like../opt/splunkforwarder/etc/apps/IND1/local/inputs.conf but it didn't work&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2013 12:03:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54502#M96848</guid>
      <dc:creator>amitj</dc:creator>
      <dc:date>2013-06-04T12:03:15Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk forwarder config not working</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54503#M96849</link>
      <description>&lt;P&gt;yes, I added to "local" directory like../opt/splunkforwarder/etc/apps/IND1/local/inputs.conf but it didn't work&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2013 12:38:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54503#M96849</guid>
      <dc:creator>amitj</dc:creator>
      <dc:date>2013-06-04T12:38:41Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk forwarder config not working</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54504#M96850</link>
      <description>&lt;P&gt;Have you also defined outputs.conf for each config?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2013 07:08:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54504#M96850</guid>
      <dc:creator>jtworzydlo</dc:creator>
      <dc:date>2013-06-05T07:08:42Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk forwarder config not working</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54505#M96851</link>
      <description>&lt;P&gt;No, do I need to define outputs.conf for this?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2013 07:09:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54505#M96851</guid>
      <dc:creator>amitj</dc:creator>
      <dc:date>2013-06-05T07:09:53Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk forwarder config not working</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54506#M96852</link>
      <description>&lt;P&gt;OK, because that's not what it said in your question...anyhow, you shouldn't need to "activate" this anywhere, just restart the Splunk instance and you should be good to go. Possible steps forward is to check btool output (&lt;CODE&gt;$SPLUNK_HOME/bin/splunk cmd btool inputs list --debug&lt;/CODE&gt;) to see if Splunk sees your defined inputs. If it does, you should check splunkd.log to see if there are any problems with the inputs you've defined.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2013 07:55:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-forwarder-config-not-working/m-p/54506#M96852</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-06-05T07:55:18Z</dc:date>
    </item>
  </channel>
</rss>

