<?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: Deployment App inputs.conf issues in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/238002#M46227</link>
    <description>&lt;P&gt;Have you looked at &lt;A href="https://wiki.splunk.com/Community:Troubleshooting_Monitor_Inputs"&gt;https://wiki.splunk.com/Community:Troubleshooting_Monitor_Inputs&lt;/A&gt; in particular  &lt;A href="https://your-splunk-server:8089/services/admin/inputstatus/TailingProcessor:FileStatus"&gt;https://your-splunk-server:8089/services/admin/inputstatus/TailingProcessor:FileStatus&lt;/A&gt; ? Can be quite helpful in seeing why files aren't being processed.&lt;/P&gt;

&lt;P&gt;My guess would be "ignoreOlderThan = 10m" is the issue.  This means that Splunk ignores any files that is older than 10minutes when it first sees the file (on startup) even if it is written to later on while Splunk is still running.  The only way to get Splunk to process the files once it has 'tagged' them as old, is to restart Splunk.&lt;/P&gt;</description>
    <pubDate>Thu, 24 Sep 2015 12:35:26 GMT</pubDate>
    <dc:creator>samhughe</dc:creator>
    <dc:date>2015-09-24T12:35:26Z</dc:date>
    <item>
      <title>Deployment App inputs.conf issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/237999#M46224</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;

&lt;P&gt;We have an issue when we are trying to collect syslogdata from a filesystem on a syslog server with help from a deployment-app. &lt;/P&gt;

&lt;P&gt;The folder structure looks like this, all data is being written to /var/log/netlogs/"IP-adress of the device"/messages.log&lt;/P&gt;

&lt;P&gt;Example structure:&lt;BR /&gt;
/var/log/netlogs/10.3.56.12/messages.log&lt;BR /&gt;
/var/log/netlogs/10.3.56.13/messages.log&lt;BR /&gt;
/var/log/netlogs/10.3.56.14/messages.log&lt;BR /&gt;
/var/log/netlogs/10.3.56.15/messages.log&lt;/P&gt;

&lt;P&gt;Here is the inputs.conf file we are using right now (we have experimented back and forward with crcSalt, initCrcLength)&lt;BR /&gt;
[monitor:///var/log/netlogs/]&lt;BR /&gt;
sourcetype = syslog&lt;BR /&gt;
whitelist = .log$&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;BR /&gt;
crcSalt = &amp;lt;string&amp;gt;&lt;BR /&gt;
initCrcLength = 6250&lt;BR /&gt;
ignoreOlderThan = 10m&lt;BR /&gt;
index = network&lt;/P&gt;

&lt;P&gt;Any ides what we need to do in order to index every single messages.conf in this filestructure&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2015 11:22:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/237999#M46224</guid>
      <dc:creator>Norling80</dc:creator>
      <dc:date>2015-09-23T11:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment App inputs.conf issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/238000#M46225</link>
      <description>&lt;P&gt;How about just this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///var/log/netlogs/*/messages.log]
sourcetype = syslog
SHOULD_LINEMERGE = false
crcSalt = &amp;lt;string&amp;gt;
initCrcLength = 6250
ignoreOlderThan = 10m
index = network
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 23 Sep 2015 16:08:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/238000#M46225</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2015-09-23T16:08:00Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment App inputs.conf issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/238001#M46226</link>
      <description>&lt;P&gt;Thanks for the answer, unfortunately that did not do the trick, we have also checked the filesystem access rights and they are all good. &lt;/P&gt;</description>
      <pubDate>Thu, 24 Sep 2015 07:37:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/238001#M46226</guid>
      <dc:creator>Norling80</dc:creator>
      <dc:date>2015-09-24T07:37:22Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment App inputs.conf issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/238002#M46227</link>
      <description>&lt;P&gt;Have you looked at &lt;A href="https://wiki.splunk.com/Community:Troubleshooting_Monitor_Inputs"&gt;https://wiki.splunk.com/Community:Troubleshooting_Monitor_Inputs&lt;/A&gt; in particular  &lt;A href="https://your-splunk-server:8089/services/admin/inputstatus/TailingProcessor:FileStatus"&gt;https://your-splunk-server:8089/services/admin/inputstatus/TailingProcessor:FileStatus&lt;/A&gt; ? Can be quite helpful in seeing why files aren't being processed.&lt;/P&gt;

&lt;P&gt;My guess would be "ignoreOlderThan = 10m" is the issue.  This means that Splunk ignores any files that is older than 10minutes when it first sees the file (on startup) even if it is written to later on while Splunk is still running.  The only way to get Splunk to process the files once it has 'tagged' them as old, is to restart Splunk.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Sep 2015 12:35:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Deployment-App-inputs-conf-issues/m-p/238002#M46227</guid>
      <dc:creator>samhughe</dc:creator>
      <dc:date>2015-09-24T12:35:26Z</dc:date>
    </item>
  </channel>
</rss>

