Nifi 2.0 Start Problem

[#1]

Hello , 

I use "nifi.cmd start" to start with NIFI.

Sometime  it works and most of the times it doesn't. 

In case  where NIFI doesn't work I am getting following logs : 

2024-11-29 21:06:39,642 INFO [main] o.a.n.w.StandardContentViewerApplication Starting StandardContentViewerApplication using Java 21.0.2 with PID 24600 (D:\WorkingInstaller\2.0\nifi-2.0.0-bin\nifi-2.0.0\work\jetty\nifi-standard-content-viewer-2.0.0.war\webapp\WEB-INF\classes started by Riyaz in D:\WorkingInstaller\2.0\nifi-2.0.0-bin\nifi-2.0.0)
2024-11-29 21:06:39,643 INFO [main] o.a.n.w.StandardContentViewerApplication No active profile set, falling back to 1 default profile: "default"

Any pointers would be appreciated.

Thanks,

Riyaz

[#2]

I have the same problem.

[#3]

@MattWho @SAMSAL @mburgess Hi! Do you have some insights here?

[#4]

I have a same problem.  Nifi.sh started and failed in next few seconds.

2025-12-31 14:03:57,387 INFO [main] org.apache.nifi.bootstrap.Command Application Process [9606] started
2025-12-31 14:03:57,388 INFO [main] org.apache.nifi.bootstrap.Command Bootstrap Process Running
2025-12-31 14:04:57,392 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process not found
2025-12-31 14:04:57,392 WARN [StartBootstrapCommand] o.a.n.b.command.StartBootstrapCommand Application monitoring failed with status [STOPPED]

---

nifi can't start with Java17 but Java21

Any pointers would be appreciated

BV

[#5]

Hello @PepeVo! As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks.

[#6]

@mohdriyaz 

These are just INFO level log lines.   What logging did you see in the NiFi bootstrap.log?  
Does the process die or does just appear hung and not progressing to point where UI is becomes available?

On the times where NiFi did start, what log lines are seen immediately after above are output?

Thanks,
Matt

[#7]

Hello,

The process hangs. The lines in mohdriyaz' screenshot are the last ones that appear. There are no errors. When quitting with ctrl-c in the CMD window, one Java process is hanging and needs to be killed with the task manager.

In cases when the start succeeds, the app log continues within a second and the memory usage of the java process increases.

I think the bootstrap log seems normal when the startup fails, for example:

2024-12-05 14:58:44,813 INFO [main] o.a.n.b.command.RunBootstrapCommand Java Version: 21.0.5+11-LTS
2024-12-05 14:58:44,813 INFO [main] o.a.n.b.command.RunBootstrapCommand Available Processors: 4
2024-12-05 14:58:44,891 INFO [main] o.a.n.b.command.RunBootstrapCommand E:\jdk21.0.5_11\bin\java.exe --class-path E:\nifi-2.0.0\lib\jcl-over-slf4j-2.0.16.jar;E:\nifi-2.0.0\lib\jul-to-slf4j-2.0.16.jar;E:\nifi-2.0.0\lib\log4j-over-slf4j-2.0.16.jar;E:\nifi-2.0.0\lib\logback-classic-1.5.12.jar;E:\nifi-2.0.0\lib\logback-core-1.5.12.jar;E:\nifi-2.0.0\lib\nifi-api-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-framework-api-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-nar-utils-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-per-process-group-logging-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-properties-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-property-utils-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-python-framework-api-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-runtime-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-server-api-2.0.0.jar;E:\nifi-2.0.0\lib\nifi-stateless-api-2.0.0.jar;E:\nifi-2.0.0\lib\slf4j-api-2.0.16.jar;E:\nifi-2.0.0\conf -Dorg.apache.nifi.bootstrap.config.log.dir=E:\nifi-2.0.0\logs -Dnifi.properties.file.path=E:\nifi-2.0.0\conf\nifi.properties -Dorg.apache.nifi.management.server.address=127.0.0.1:52020 -Djavax.security.auth.useSubjectCredsOnly=true -Xmx10g -Djava.awt.headless=true -Xms5g -Dsun.net.http.allowRestrictedHeaders=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dcurator-log-only-first-connection-issue-as-error-level=true org.apache.nifi.NiFi
2024-12-05 14:58:44,922 INFO [main] org.apache.nifi.bootstrap.Command Application Process [10636] started
2024-12-05 14:58:44,922 INFO [main] org.apache.nifi.bootstrap.Command Bootstrap Process Running
2024-12-05 14:59:44,939 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [10636] running
2024-12-05 14:59:44,939 INFO [StartBootstrapCommand] o.a.n.b.command.StartBootstrapCommand Application monitoring started
2024-12-05 14:59:49,954 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [10636] running
2024-12-05 14:59:54,955 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [10636] running

And keeps repeating the same line until you kill it.

Thanks,

[#8]

I attach a screenshot of the log when the start succeeds.

 

[#9]

@Dahlgren @mohdriyaz 

Before launching did you check to make sure all the previous running NiFi java process were gone?

Can you share more detail about your environments (Windows version and  Java version)?

Any details on the Java process you have to terminate after quitting with ctrl-c in the CMD window?

Thanks,
Matt

[#10]

Yes, I kill the Java process before trying again. After trying 5-10 times, NiFi normally starts.

Windows Server 2022 Datacenter, 21H2

The Java version is Corretto-21.0.5.11.1, and I also tried Zulu 21.38+21-CA, both have the problem.

Not sure, but I think it’s the bootstrap process that ends with ctrl-c, while the application process remains hung and must be killed with the task manager.