if this was during the file handling exhaustion issue you'll see a lot
of undesirable behaviors.  If this is happening when file handles are
not a problem then it will require deeper digging.  That said, the
base configuration does indeed write to nifi-app.log and roll over in
the expected manner (at least in all cases I've seen).

On Thu, Oct 27, 2016 at 9:07 AM, Joe Gresock <jgres...@gmail.com> wrote:
> I'll try that, though I believe we removed the .%i because it continued to
> make logs more than the configured <maxHistory>10</maxHistory> when rolling
> over, which ran us out of disk space.
>
> On Thu, Oct 27, 2016 at 1:00 PM, Joe Witt <joe.w...@gmail.com> wrote:
>
>> Joe
>>
>> I suspect you want to get closer to the original entry with the %i
>> part.  So perhaps
>>
>> <fileNamePattern>/opt/nifi/data/logs/nifi-app_%d{yyyy-MM-dd_HH}.%i.log</
>> fileNamePattern>
>>
>> Thanks
>> Joe
>>
>> On Thu, Oct 27, 2016 at 8:57 AM, Joe Gresock <jgres...@gmail.com> wrote:
>> > 23c23
>> > <
>> > <file>${org.apache.nifi.bootstrap.config.log.dir}/nifi-app.log</file>
>> > ---
>> >>         <file>/opt/nifi/data/logs/nifi-app.log</file>
>> > 31c31
>> > <
>> > <fileNamePattern>${org.apache.nifi.bootstrap.config.log.dir}
>> /nifi-app_%d{yyyy-MM-dd_HH}.%i.log</fileNamePattern>
>> > ---
>> >>
>> > <fileNamePattern>/opt/nifi/data/logs/nifi-app_%d{yyyy-MM-
>> dd_HH}.log</fileNamePattern>
>> > 36c36,55
>> > <             <maxHistory>30</maxHistory>
>> > ---
>> >>             <maxHistory>10</maxHistory>
>> >
>> >
>> > On Thu, Oct 27, 2016 at 12:39 PM, Joe Witt <joe.w...@gmail.com> wrote:
>> >
>> >> Joe
>> >>
>> >> Can you highlight any changes (diff) from the standard configuration
>> >> provided?
>> >>
>> >> Thanks
>> >> Joe
>> >>
>> >> On Thu, Oct 27, 2016 at 8:34 AM, Joe Gresock <jgres...@gmail.com>
>> wrote:
>> >> > Before I create a ticket, I wanted to see if anyone had run into this.
>> >> >
>> >> > Whenever we restart nifi, the nifi-app.log no longer gets written to.
>> >> >
>> >> > If I delete all the nifi-app* logs and then restart, it writes logs
>> just
>> >> > fine, but if I leave the logs it doesn't write to the log upon
>> restarting
>> >> > nifi.
>> >> >
>> >> > Sure enough, "lsof | grep nifi-app" produces output prior to restart,
>> but
>> >> > produces nothing after a restart (if I have not deleted the logs).
>> >> >
>> >> > An excerpt from my logback.xml:
>> >> >
>> >> > <configuration scan="true" scanPeriod="30 seconds">
>> >> >     <contextListener
>> >> > class="ch.qos.logback.classic.jul.LevelChangePropagator">
>> >> >         <resetJUL>true</resetJUL>
>> >> >     </contextListener>
>> >> >
>> >> >     <appender name="APP_FILE"
>> >> > class="ch.qos.logback.core.rolling.RollingFileAppender">
>> >> >         <file>/opt/nifi/data/logs/nifi-app.log</file>
>> >> >         <rollingPolicy
>> >> > class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
>> >> >             <!--
>> >> >               For daily rollover, use 'app_%d.log'.
>> >> >               For hourly rollover, use 'app_%d{yyyy-MM-dd_HH}.log'.
>> >> >               To GZIP rolled files, replace '.log' with '.log.gz'.
>> >> >               To ZIP rolled files, replace '.log' with '.log.zip'.
>> >> >             -->
>> >> >
>> >> > <fileNamePattern>/opt/nifi/data/logs/nifi-app_%d{yyyy-MM-
>> >> dd_HH}.log</fileNamePattern>
>> >> >             <timeBasedFileNamingAndTriggeringPolicy
>> >> > class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
>> >> >                 <maxFileSize>100MB</maxFileSize>
>> >> >             </timeBasedFileNamingAndTriggeringPolicy>
>> >> >             <maxHistory>10</maxHistory>
>> >> >         </rollingPolicy>
>> >> >         <encoder
>> >> > class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
>> >> >             <pattern>%date %level [%thread] %logger{40}
>> %msg%n</pattern>
>> >> >             <immediateFlush>true</immediateFlush>
>> >> >         </encoder>
>> >> >     </appender>
>> >> >     <root level="INFO">
>> >> >         <appender-ref ref="APP_FILE"/>
>> >> >     </root>
>> >> > </configuration>
>> >> >
>> >> >
>> >> > --
>> >> > I know what it is to be in need, and I know what it is to have
>> plenty.  I
>> >> > have learned the secret of being content in any and every situation,
>> >> > whether well fed or hungry, whether living in plenty or in want.  I
>> can
>> >> do
>> >> > all this through him who gives me strength.    *-Philippians 4:12-13*
>> >>
>> >
>> >
>> >
>> > --
>> > I know what it is to be in need, and I know what it is to have plenty.  I
>> > have learned the secret of being content in any and every situation,
>> > whether well fed or hungry, whether living in plenty or in want.  I can
>> do
>> > all this through him who gives me strength.    *-Philippians 4:12-13*
>>
>
>
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can do
> all this through him who gives me strength.    *-Philippians 4:12-13*

Reply via email to