<?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>question Re: tailfile logfile formant WD-YYYYMMDD.log in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/tailfile-logfile-formant-WD-YYYYMMDD-log/m-p/144152#M40226</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;At this moment this kind of scenario is not really supported. The processor expects that log messages are appended to a file with a fixed name. Something like:&lt;/P&gt;&lt;P&gt;- /my/var/log/my-app.log&lt;/P&gt;&lt;P&gt;- /my/var/log/my-app.log.1&lt;/P&gt;&lt;P&gt;- /my/var/log/my-app.log.2&lt;/P&gt;&lt;P&gt;Messages being appended to 'my-app.log'.&lt;/P&gt;&lt;P&gt;A workaround would be to update your processor every day with a script/crontab to change the filename and rolling filename properties.&lt;/P&gt;&lt;P&gt;There is a PR to support the scenario you are describing [1] and it is currently in a review process. You can give it a try if you are in position to, otherwise it will probably make it in the next version of NiFi (1.1.0 I think).&lt;/P&gt;&lt;P&gt;[1] &lt;A href="https://github.com/apache/nifi/pull/980" target="_blank"&gt;https://github.com/apache/nifi/pull/980&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Sep 2016 15:20:37 GMT</pubDate>
    <dc:creator>pvillard</dc:creator>
    <dc:date>2016-09-09T15:20:37Z</dc:date>
    <item>
      <title>tailfile logfile formant WD-YYYYMMDD.log</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/tailfile-logfile-formant-WD-YYYYMMDD-log/m-p/144151#M40225</link>
      <description>&lt;P&gt;Hello experts,&lt;/P&gt;&lt;P&gt;I am trying to copy the files being written using tailfile-&amp;gt; putfile. Format of files are below. &lt;/P&gt;&lt;P&gt;WD-YYYYMMDD.log&lt;/P&gt;&lt;P&gt;At any point of time latest file will be get written(ex. WD-20160908.log) and next it will be switched to new date (ex. WD-20160909.log)and that file start getting written.&lt;/P&gt;&lt;P&gt;File to tail : /root/wd/log1/WD-20160831.log&lt;/P&gt;&lt;P&gt;Rolling FileName Pattern: WD-*.log&lt;/P&gt;&lt;P&gt;State of file:&lt;/P&gt;&lt;P&gt;Initial start position: Beginning of File&lt;/P&gt;&lt;P&gt;File location : local&lt;/P&gt;&lt;P&gt;Results are not looks correct. Please suggested. &lt;/P&gt;&lt;PRE&gt;At source :

[root@server1 log1]# cat &amp;gt; WD-20160830.log
1
2
3
^C
[root@server1 log1]# cat &amp;gt;&amp;gt; WD-20160831.log
4
5
6
^C
[root@server1 log1]# ls -ltr
total 8
-rw-r--r--. 1 root root 6 Sep  9 00:53 WD-20160830.log
-rw-r--r--. 1 root root 6 Sep  9 00:54 WD-20160831.log


At target:


[root@server1 log2]# ls -tlr
total 12
-rw-r--r--. 1 nifi hadoop 2 Sep  9 00:53 WD-20160830.log
-rw-r--r--. 1 nifi hadoop 4 Sep  9 00:54 WD-20160831.0-4.log
-rw-r--r--. 1 nifi hadoop 2 Sep  9 00:54 WD-20160831.4-6.log
[root@*****log2]# cat WD-20160830.log
1
[root@server1 log2]# cat WD-20160831.0-4.log
4
5
[root@server1 log2]# cat WD-20160831.4-6.log
6

&lt;/PRE&gt;</description>
      <pubDate>Fri, 09 Sep 2016 15:04:01 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/tailfile-logfile-formant-WD-YYYYMMDD-log/m-p/144151#M40225</guid>
      <dc:creator>deepeshbhatia21</dc:creator>
      <dc:date>2016-09-09T15:04:01Z</dc:date>
    </item>
    <item>
      <title>Re: tailfile logfile formant WD-YYYYMMDD.log</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/tailfile-logfile-formant-WD-YYYYMMDD-log/m-p/144152#M40226</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;At this moment this kind of scenario is not really supported. The processor expects that log messages are appended to a file with a fixed name. Something like:&lt;/P&gt;&lt;P&gt;- /my/var/log/my-app.log&lt;/P&gt;&lt;P&gt;- /my/var/log/my-app.log.1&lt;/P&gt;&lt;P&gt;- /my/var/log/my-app.log.2&lt;/P&gt;&lt;P&gt;Messages being appended to 'my-app.log'.&lt;/P&gt;&lt;P&gt;A workaround would be to update your processor every day with a script/crontab to change the filename and rolling filename properties.&lt;/P&gt;&lt;P&gt;There is a PR to support the scenario you are describing [1] and it is currently in a review process. You can give it a try if you are in position to, otherwise it will probably make it in the next version of NiFi (1.1.0 I think).&lt;/P&gt;&lt;P&gt;[1] &lt;A href="https://github.com/apache/nifi/pull/980" target="_blank"&gt;https://github.com/apache/nifi/pull/980&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Sep 2016 15:20:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/tailfile-logfile-formant-WD-YYYYMMDD-log/m-p/144152#M40226</guid>
      <dc:creator>pvillard</dc:creator>
      <dc:date>2016-09-09T15:20:37Z</dc:date>
    </item>
  </channel>
</rss>

