Support Questions

Find answers, ask questions, and share your expertise

Not able to start NiFi cluster

avatar
Contributor

Hi All,

Greeting for the day.

Not able to start nifi cluster.

below error occur in nifi-bootstrap.log:

2018-10-15 12:02:08,321 ERROR [NiFi logging handler] org.apache.nifi.StdErr SLF4J: Class path contains multiple SLF4J bindings. 2018-10-15 12:02:08,321 ERROR [NiFi logging handler] org.apache.nifi.StdErr SLF4J: Found binding in [jar:file:/usr/hdf/2.1.1.0-2/nifi/lib/phoenix-client.jar!/org/slf4j/impl/StaticLoggerBinder.class] 2018-10-15 12:02:08,321 ERROR [NiFi logging handler] org.apache.nifi.StdErr SLF4J: Found binding in [jar:file:/usr/hdf/2.1.1.0-2/nifi/lib/logback-classic-1.1.3.jar!/org/slf4j/impl/StaticLoggerBinder.class] 2018-10-15 12:02:08,322 ERROR [NiFi logging handler] org.apache.nifi.StdErr SLF4J: Found binding in [jar:file:/usr/hdf/2.1.1.0-2/nifi/lib/phoenix-4.7.0.2.5.3.0-37-client.jar!/org/slf4j/impl/StaticLoggerBinder.class] 2018-10-15 12:02:08,322 ERROR [NiFi logging handler] org.apache.nifi.StdErr SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 2018-10-15 12:02:08,340 ERROR [NiFi logging handler] org.apache.nifi.StdErr log4j:WARN No appenders could be found for logger (org.apache.nifi.NiFi). 2018-10-15 12:02:08,340 ERROR [NiFi logging handler] org.apache.nifi.StdErr log4j:WARN Please initialize the log4j system properly. 2018-10-15 12:02:08,340 ERROR [NiFi logging handler] org.apache.nifi.StdErr log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. 2018-10-15 12:02:08,899 INFO [NiFi Bootstrap Command Listener] org.apache.nifi.bootstrap.RunNiFi Apache NiFi now running and listening for Bootstrap requests on port 44274 2018-10-15 12:02:39,239 INFO [main] org.apache.nifi.bootstrap.RunNiFi NiFi never started. Will not restart NiFi

Thanks in Advance.

1 ACCEPTED SOLUTION

avatar
Master Mentor
@Amit Mishra

-

Based on the ERROR above it appears someone has added a non standard jar file to NiFi's default lib directory:

phoenix-4.7.0.2.5.3.0-37-client.jar . --> added to :/usr/hdf/2.1.1.0-2/nifi/lib/ directory

-

First thing I would try is removing this file from NiFi's default lib directory on every NiFi node. Then restart your NIFi cluster to make sure ERROR goes away.

-

Then if you find you need this jar for something in your dataflow, perhaps try creating a new custom lib directory in NiFi and adding it there. This done by simply adding a new property in the nifi.properties file:

-

1. Create a new custom lib directory on each of the NiFi nodes (for example: /var/lib/nifi/custom-lib/)

2. Move your custom phoenix-4.7.0.2.5.3.0-37-client.jar in to that new directory. (Recommend moving any other custom added jar/nar files here as well. You should not be adding any non standard files to NiFI's default lib directory.)

3. Make sure property directory and file ownership and permissions are set.

4. Add new custom property named: nifi.nar.library.directory.custom1= . (custom1 is an example and can be set to whatever you like.)

5. Set this new properties value to teh path to your custom lib directory you created on each node. (for example: nifi.nar.library.directory.custom1=/var/lib/nifi/custom-lib/ )

6. Restart all your NiFi nodes.

7. Verify ERROR still does not appear.

-

Thank you,

Matt

-

If you found this answer addressed your question, please take a moment to login in and click the "ACCEPT" link.

View solution in original post

2 REPLIES 2

avatar
Master Mentor
@Amit Mishra

-

Based on the ERROR above it appears someone has added a non standard jar file to NiFi's default lib directory:

phoenix-4.7.0.2.5.3.0-37-client.jar . --> added to :/usr/hdf/2.1.1.0-2/nifi/lib/ directory

-

First thing I would try is removing this file from NiFi's default lib directory on every NiFi node. Then restart your NIFi cluster to make sure ERROR goes away.

-

Then if you find you need this jar for something in your dataflow, perhaps try creating a new custom lib directory in NiFi and adding it there. This done by simply adding a new property in the nifi.properties file:

-

1. Create a new custom lib directory on each of the NiFi nodes (for example: /var/lib/nifi/custom-lib/)

2. Move your custom phoenix-4.7.0.2.5.3.0-37-client.jar in to that new directory. (Recommend moving any other custom added jar/nar files here as well. You should not be adding any non standard files to NiFI's default lib directory.)

3. Make sure property directory and file ownership and permissions are set.

4. Add new custom property named: nifi.nar.library.directory.custom1= . (custom1 is an example and can be set to whatever you like.)

5. Set this new properties value to teh path to your custom lib directory you created on each node. (for example: nifi.nar.library.directory.custom1=/var/lib/nifi/custom-lib/ )

6. Restart all your NiFi nodes.

7. Verify ERROR still does not appear.

-

Thank you,

Matt

-

If you found this answer addressed your question, please take a moment to login in and click the "ACCEPT" link.

avatar
Contributor

Thank you Matt.