I didn't realize that. I'll see if -F is available in my case. Thank you very much Andrew. -Jim
On Thu, Aug 17, 2017 at 5:36 PM, Andrew Grande <[email protected]> wrote: > Typically this is better handled by using the -F switch instead of -f, it > has more robust file handling and manages files disappearing correctly. > Unfortunately, some OS don't have that switch in their toolchain. > > Andrew > > On Thu, Aug 17, 2017, 5:07 PM James McMahon <[email protected]> wrote: > >> Interesting. Thank you Russ. I wonder whether I somehow interrupted or >> deleted the log file when I "ctrl-C"`ed out of the tail -f ? I'll have to >> test that and see. -Jim >> >> On Thu, Aug 17, 2017 at 4:57 PM, Russell Bateman <[email protected]> >> wrote: >> >>> James, >>> >>> It's the case that, NiFi running, deleting a log file will result in >>> that file no longer existing and no longer written to again until NiFi is >>> restarted. This is my observation anyway. >>> >>> Hope this observation is useful. >>> >>> Russ >>> >>> On 08/17/2017 02:11 PM, James McMahon wrote: >>> >>> 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 >>>> >>> >>>> >>> >>>> >>> >>>> > >>>> > >>>> <[email protected]> <[email protected]> <[email protected]> >>>> >>> >>> >>> >>
