<?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: How to configure parameter for TailingProcessor to automatically retry reading a file after failing? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114008#M97632</link>
    <description>&lt;P&gt;Before ask Splunk to do this more times, have you checked:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Does the file exist?&lt;/LI&gt;
&lt;LI&gt;Splunk is running under some user credentials. Is this file accessible by that user?&lt;/LI&gt;
&lt;LI&gt;Does another process have the file locked so that Splunk cannot read it?&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Sat, 06 Sep 2014 23:41:10 GMT</pubDate>
    <dc:creator>lguinn2</dc:creator>
    <dc:date>2014-09-06T23:41:10Z</dc:date>
    <item>
      <title>How to configure parameter for TailingProcessor to automatically retry reading a file after failing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114007#M97631</link>
      <description>&lt;P&gt;It took a while to copy the large logfile over the slow network, and it looks like the TailingProcessor gave up after 2 tries:&lt;BR /&gt;
&lt;PRE&gt;&lt;CODE&gt;&lt;BR /&gt;
09-06-2014 15:17:03.607 -0700 WARN  FileClassifierManager - Unable to open 'D:\Logs\syslog2014-09-05'.&lt;BR /&gt;
09-06-2014 15:17:03.607 -0700 WARN  FileClassifierManager - The file 'D:\Logs\syslog2014-09-05' is invalid. Reason: cannot_read&lt;BR /&gt;
09-06-2014 15:17:03.607 -0700 INFO  TailingProcessor - Ignoring file 'D:\Logs\syslog2014-09-05' due to: cannot_read&lt;BR /&gt;
09-06-2014 15:22:47.707 -0700 WARN  FileClassifierManager - Unable to open 'D:\Logs\syslog2014-09-05'.&lt;BR /&gt;
09-06-2014 15:22:47.707 -0700 WARN  FileClassifierManager - The file 'D:\Logs\syslog2014-09-05' is invalid. Reason: cannot_read&lt;BR /&gt;
09-06-2014 15:22:47.707 -0700 INFO  TailingProcessor - Ignoring file 'D:\Logs\syslog2014-09-05' due to: cannot_read&lt;BR /&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;Any way to make it automatically retry a couple more times (via some configuration parameter somewhere)?&lt;BR /&gt;
Using Splunk v6.1.3 for Windows.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:30:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114007#M97631</guid>
      <dc:creator>NK_1</dc:creator>
      <dc:date>2020-09-28T17:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure parameter for TailingProcessor to automatically retry reading a file after failing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114008#M97632</link>
      <description>&lt;P&gt;Before ask Splunk to do this more times, have you checked:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Does the file exist?&lt;/LI&gt;
&lt;LI&gt;Splunk is running under some user credentials. Is this file accessible by that user?&lt;/LI&gt;
&lt;LI&gt;Does another process have the file locked so that Splunk cannot read it?&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Sat, 06 Sep 2014 23:41:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114008#M97632</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-09-06T23:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure parameter for TailingProcessor to automatically retry reading a file after failing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114009#M97633</link>
      <description>&lt;OL&gt;
&lt;LI&gt;Yes.&lt;/LI&gt;
&lt;LI&gt;Yes.&lt;/LI&gt;
&lt;LI&gt;Yes, during the slow copy process.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;If the file was small and/or the copy process was fast, Splunk indexes the file fine.&lt;/P&gt;</description>
      <pubDate>Sat, 06 Sep 2014 23:51:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114009#M97633</guid>
      <dc:creator>NK_1</dc:creator>
      <dc:date>2014-09-06T23:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure parameter for TailingProcessor to automatically retry reading a file after failing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114010#M97634</link>
      <description>&lt;P&gt;Is there any way to set the copy process so that that it doesn't lock the file?&lt;/P&gt;

&lt;P&gt;Is it possible to forward the file from its original location?&lt;/P&gt;</description>
      <pubDate>Sun, 07 Sep 2014 06:45:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-parameter-for-TailingProcessor-to-automatically/m-p/114010#M97634</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-09-07T06:45:48Z</dc:date>
    </item>
  </channel>
</rss>

