CODEWITHSUNDEEP
apache-nifi
fifi.h
fifi.h

Reputation: 13

NiFi not launching

INFO [main] org.apache.nifi.bootstrap.Command Apache NiFi is currently running, listening to Bootstrap on port 20740, PID=31405

That means NiFi is running, and I can see its log in logs/nifi-app.log.

The UI is available at https://servername:9443/nifi. It successfully initiated communication with Bootstrap.

But i have this error, and the UI fails to appear. Do you have any solutions?

Failed to invoke @OnEnabled method of JettyWebSocketServer[id=01591009-1d2b-177f-e304-a7cc87d735ce] due to java.net.BindException: Address already in use

Upvotes: 0

Views: 3351

Answers (2)

Bryan Bende
Bryan Bende

Reputation: 18670

"java.net.BindException: Address already in use" means a port is already in use by something else on your system.

In this case it shows that it is coming from the JettyWebSocketServer controller service which is trying to bind to port 9998.

You can use "netstat -lntp" to see what is using port 9998. It could also be possible that you have more than one instance of the controller service with both of them configured with port 9998 and one of them is binging to it and the other fails.

Upvotes: 3

Ben Yaakobi
Ben Yaakobi

Reputation: 1668

Seems like a Controller Service that fails... Try browsing your flow.xml.gz and check for any ControllerServices named JettyWebSocketServer. Change their <state></state> from <state>ENABLED</state> to <state>DISABLED</state> and try running NiFi again. You can tell it is a controller service by the @enabledannotation which invokes a method that needs to run when the controller service is enabled.

NiFi shouldn't fail to start because of a failing controller service but it seems to be the problem(probably a bug).

After it start back up, you can configure the controller service to run on a different port.

I also suggest, that if it is the case, that you open an issue to Apache about this since it seems like a pretty major bug.

Upvotes: 1

Related Questions