<?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: Why does my Splunk universal forwarder monitor stop processing files the next day after they roll over? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230270#M44810</link>
    <description>&lt;P&gt;No, no headers.  It's all unique, with timestamps. &lt;/P&gt;</description>
    <pubDate>Tue, 12 Jan 2016 15:49:11 GMT</pubDate>
    <dc:creator>a212830</dc:creator>
    <dc:date>2016-01-12T15:49:11Z</dc:date>
    <item>
      <title>Why does my Splunk universal forwarder monitor stop processing files the next day after they roll over?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230268#M44808</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a Splunk Universal Forwarder running on Windows 2012,  monitoring a bunch of files in different folders.  The files are monitored fine, until the next day, when they stop.   No idea why.   The files are in the format &lt;CODE&gt;someUniqueIdentifier_hostname_MM-DD-YYYY_HHMMSS.txt&lt;/CODE&gt;.  &lt;/P&gt;

&lt;P&gt;Here are some examples:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;VMHostConfig_ABCC002VWIN.FMR.COM_01-01-2016_012804.txt
VMHostConfig_ABCC002VWIN.FMR.COM_01-02-2016_012801.txt
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;My inputs looks like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://D:\productionscriptdata\vmhost_config\VMHostConfig_*.txt]
index = distributed
sourcetype = vmhostconfig
followTail = 0
crcSalt = &amp;lt;SOURCE&amp;gt;
ignoreOlderThan = 7d
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any suggestions?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jan 2016 15:14:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230268#M44808</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2016-01-12T15:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: Why does my Splunk universal forwarder monitor stop processing files the next day after they roll over?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230269#M44809</link>
      <description>&lt;P&gt;Do these files all happen to have the same headers? Sometimes if the header length is over the default of 256bytes, Splunk won't recognize a rolled file. Check the inputs.conf spec for :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;initCrcLength = &amp;lt;integer&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;UL&gt;
&lt;LI&gt;This setting adjusts how much of a file Splunk reads before trying to identify whether it is a file that has
already been seen.  You may want to adjust this if you have many files with common headers (comment headers,
long CSV headers, etc) and recurring filenames.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Change that to a larger value..&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jan 2016 15:33:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230269#M44809</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2016-01-12T15:33:21Z</dc:date>
    </item>
    <item>
      <title>Re: Why does my Splunk universal forwarder monitor stop processing files the next day after they roll over?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230270#M44810</link>
      <description>&lt;P&gt;No, no headers.  It's all unique, with timestamps. &lt;/P&gt;</description>
      <pubDate>Tue, 12 Jan 2016 15:49:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230270#M44810</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2016-01-12T15:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: Why does my Splunk universal forwarder monitor stop processing files the next day after they roll over?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230271#M44811</link>
      <description>&lt;P&gt;Are the files older than the 7d limit? I know that's too easy &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;
Was there anything in the &lt;CODE&gt;splunkd.log&lt;/CODE&gt; corresponding to that monitor input? You can turn on debug mode for that component (&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/Troubleshooting/Enabledebuglogging"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.2/Troubleshooting/Enabledebuglogging&lt;/A&gt; ), or restart splunk on that forwarder with debug mode by running &lt;CODE&gt;./splunk restart --debug&lt;/CODE&gt; (although I think it no longer exists for windows forwarders - i forget)&lt;/P&gt;

&lt;P&gt;What technology generates the new files? Might be worth seeing if other folks have had issues with that and splunk?&lt;/P&gt;

&lt;P&gt;Some may suggest the &lt;CODE&gt;alwaysOpenFile&lt;/CODE&gt; setting but I say wait until support has you implement that because of the performance issues.&lt;/P&gt;

&lt;P&gt;That said, if you can't find evidence of this, nor any blocking within metrics.log, you should consider a support ticket as it sounds like the feature is not working as documented/expected.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 17:50:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230271#M44811</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2016-01-21T17:50:36Z</dc:date>
    </item>
    <item>
      <title>Re: Why does my Splunk universal forwarder monitor stop processing files the next day after they roll over?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230272#M44812</link>
      <description>&lt;P&gt;Check your splunkd.logs and metrics.log if you can find any errors.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jan 2016 03:21:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-my-Splunk-universal-forwarder-monitor-stop-processing/m-p/230272#M44812</guid>
      <dc:creator>prakash007</dc:creator>
      <dc:date>2016-01-22T03:21:59Z</dc:date>
    </item>
  </channel>
</rss>

