Hello Joe,
 
It is a VM with Rocky 8 as OS. We use the systemd to start/stop nifi process
 
The nifi process is die. I could see with the journalctl -u nifi
 
Oct 27 14:53:11 server01 systemd[1]: Started Apache NiFi.
Oct 28 03:31:04 server01 systemd[1]: nifi.service: Supervising process 1399442 which is not our child. We'll most likely not notice when it exits.
Oct 28 07:20:40 server01 bash[1399411]: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
Oct 28 07:20:40 server01 bash[1399411]: NiFi PID [1399442] shutdown started
Oct 28 07:20:40 server01 bash[1399411]: NiFi PID [1399442] shutdown in progress...
Oct 28 07:21:00 server01 bash[1399411]: NiFi has not finished shutting down after 20 seconds. Killing process.
Oct 28 07:21:04 server01 systemd[1]: nifi.service: Main process exited, code=exited, status=143/n/a
Oct 28 07:21:04 server01 systemd[1]: nifi.service: Failed with result 'exit-code'.
 
And I don't see the "Java Heap Space" error in the nifi-app.log so it is a bit weird.
It is why I'm trying to find some informations in the diagnosticts logs
 
Minh
 
Envoyé: samedi 28 octobre 2023 à 23:35
De: "Joe Witt" <[email protected]>
À: [email protected]
Objet: Re: Analyze : "Diagnostics on Stop" logs
Hello
 
We need to better understand what it means to say the node stopped.  Did the nifi process die?  The nifi-app.log should almost certainly expose something interesting.  Is this on a Linux box, or in a container, etc. How is it run and what precisely stopped?

Thanks
 
On Sat, Oct 28, 2023 at 2:28 PM <[email protected]> wrote:
Hello all,
 
I have activated the "diagnosticts on stop" in the nifi.properties.

https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#nifi_diagnostics

My node has stop twice time now but I don't find anything.
 
Have we got some documentations about the log of diagnosticts to find the root cause/ the processor cause the stop ?
 
Regards 
 
Minh
 
 
 

Reply via email to