Hi Pierre. Very interesting you ask that. While we do not, when I last
performed the service nifi stop/start, I was indeed employing a 'tail -f
./nifi-app.log' so that I could see when the jetty server was ready to
support access through the UI. Why do you ask about this?

Jim

On Thu, Aug 17, 2017 at 4:14 PM, Pierre Villard <[email protected]
> wrote:

> Hi James,
>
> Out of curiosity do you have a TailFile processor configured to tail the
> NiFi log file?
>
> Thanks
>
>
> Le 17 août 2017 22:11, "James McMahon" <[email protected]> a écrit :
>
> Thank you Joe. I agree and will monitor it closely going forward. I
> suspect there were some external factors at play here.
>
> On Thu, Aug 17, 2017 at 4:05 PM, Joe Witt <[email protected]> wrote:
>
>> Ok if 50,000 is the max then i'm doubtful that it ran out.
>>
>> In the event of exhaustion of allowed open file handle count NiFi will
>> run but its behavior will be hard to reason over.  That means it
>> cannot create any new files or open existing files but can merely
>> operate using the handles it already has. It is a situation to avoid.
>>
>> As far as what actually happened resulting in logfile issues it is not
>> easy to tell at this stage but should be monitored for system state
>> when it happens again.
>>
>> Thanks
>>
>>
>> On Thu, Aug 17, 2017 at 1:02 PM, James McMahon <[email protected]>
>> wrote:
>> > 50,000.
>> > Is NiFi robust enough that it can continue to run without the log file
>> for
>> > write attempts?
>> > It is back up and running like a champ now, so I will keep an eye on it.
>> >
>> > On Thu, Aug 17, 2017 at 3:40 PM, Joe Witt <[email protected]> wrote:
>> >>
>> >> It sounds like a case of exhausted file handles.
>> >>
>> >> Ulimit -a
>> >>
>> >> How many open files are allowed for the user nifi runs as?
>> >>
>> >> On Aug 17, 2017 12:26 PM, "James McMahon" <[email protected]>
>> wrote:
>> >>>
>> >>> Our nifi instance appeared to be running fine but we noticed that
>> there
>> >>> were no log files for today in the logs subdirectory. We could not
>> find any
>> >>> nifi logs for today anywhere on our system.
>> >>>
>> >>> I was surprised that NiFi continued to run. Has anyone experienced
>> such
>> >>> behavior?
>> >>>
>> >>> How is NiFi able to continue to run without a nifi-app.log - do all
>> its
>> >>> log messages effectively go to bit bucket heaven?
>> >>>
>> >>> I ultimately did an orderly shutdown via
>> >>> service nifi stop
>> >>> and an orderly start via
>> >>> service nifi start
>> >>> after which the log files were there as expected.
>> >>>
>> >>> Thanks in advance for any insights. -Jim
>> >>>
>> >>>
>> >>>
>> >
>> >
>>
>
>
>

Reply via email to