I don't think rebooting the system had anything to do with NiFi's ability to startup. But i'm not sure I understand that particular part of logic in the code in terms of the case it was defending against.
On Thu, May 25, 2017 at 9:34 AM, James McMahon <jsmcmah...@gmail.com> wrote: > Will do Joe. I'll dig for that now. > > Infrastructure Group did reboot the box, which had been up and running for > nearly two months. NiFi did indeed come up following the reboot. I still > want to try and get you this log information so that I can learn what > triggers such a situation, and whether there is a more refined way to solve > it than full system reboot. There are other things running on the resource > and I should try to minimize impact to them by fully rebooting. > > Let me see about that log content. Thank you again. > > On Thu, May 25, 2017 at 9:25 AM, Joe Witt <joe.w...@gmail.com> wrote: >> >> Jim, >> >> The code relevant to that log output is here [1]. Can you share the >> bootstrap output before/after that output? >> >> [1] >> https://github.com/apache/nifi/blob/rel/nifi-0.7.1/nifi-bootstrap/src/main/java/org/apache/nifi/bootstrap/RunNiFi.java >> >> Thanks >> Joe >> >> On Thu, May 25, 2017 at 9:11 AM, James McMahon <jsmcmah...@gmail.com> >> wrote: >> > Am running NiFi 0.7.x. Have been running with great stability for a long >> > period of time. Tried this morning to make this change in my >> > nifi.properties >> > conf file: >> > >> > nifi.content.repository.archive.max.retention.period=1 hour >> > >> > Reduced from the default of 12 hours. Relatively simple change, requires >> > a >> > nifi restart to take effect. >> > >> > My restart attempt throws no errors to the nifi app log, but in the >> > bootstrap log I do see this: >> > org.apache.nifi.bootstrap.RunNiFi Status file no longer exists. Will not >> > restart NiFi >> > >> > I've done some digging and all I could find is rebooting the box in >> > hopes of >> > resolving. Am reaching out to the infrastructure group that owns the >> > server >> > now, asking them to do so. Would like to also in parallel understand why >> > this happened, and where, exactly, this status file should be? >> > >> > Can I resolve this by manually recreating such a status file with >> > certain >> > permissions and ownership? >> > >> > Thanks in advance for your help. -Jim >> > >> > > >
