Re: Unable to Start NiFi Cluster After Upgrading to Version 1.21.0 from 1.16.0

[Bryan Bende]

Hello,

We would need to see more information about the error besides that single
line, there should be a whole stacktrace that we would need to see.

Thanks,

Bryan

On Mon, Jul 31, 2023 at 9:49 AM Pallavi Metkar 
wrote:

> Hi Team,
>
> I have upgraded the Apache NiFi cluster from 1.16.0 to 1.21.0. After
> completing the upgrade NiFi is not working.
>
> I am getting below error for the same:
>
> o.a.n.f.r.ConflictResolvingExternalResourceProviderWorker Error during
> polling for external resources
>
> I had tried to resolve the error but was not able to do so.
> Can you please help?
>
> Thank you
>
> Regards
> Pallavi
>

Unable to Start NiFi Cluster After Upgrading to Version 1.21.0 from 1.16.0

[Pallavi Metkar]

Hi Team,

I have upgraded the Apache NiFi cluster from 1.16.0 to 1.21.0. After
completing the upgrade NiFi is not working.

I am getting below error for the same:

o.a.n.f.r.ConflictResolvingExternalResourceProviderWorker Error during
polling for external resources

I had tried to resolve the error but was not able to do so.
Can you please help?

Thank you

Regards
Pallavi

Re: Unable to start NIFI

[Mark Payne]

Hi Richard,

It appears that you do not have the correct bin/ directory. You’ll need to make 
sure that if you’re using the source download that you’ve built using Maven. 
Then, you’ll find the bin/ directory under 
nifi-assembly/target/nifi-1.12.1-bin/nifi-1.12.1/bin/

The bin/ directory that you are looking at is part of the source code that 
contains the nifi.sh script, etc. for building the package.

Though it may make more sense just to download and use the nifi binary that is 
already built, unless you’re intentionally building because of updates made - 
but then I would expect you to building from the “main” branch instead of an 
already-released 1.12.1

Thanks
-Mark


On Jun 7, 2021, at 6:04 AM, Honey, Richard (ELS-OXF) 
mailto:r.ho...@elsevier.com>> wrote:

[cid:image002.jpg@01D75B8C.DB6B9990]


Hi NIFI team
I am struggling to understand what I have missed on implementing NIFI on my 
windows laptop?

Same error every time -> Could not find or load class 
org.apache.nifi.bootstrap.RunNiFi

I have installed both version just in case one has issue neither work

[cid:image006.jpg@01D75B8C.DB6B9990]

Bin directory is in the depths of the folder
nifi-1.12.1\nifi-1.12.1\nifi-nar-bundles\nifi-framework-bundle\nifi-framework\nifi-resources\src\main\resources\bin>
Tried running bat as admin still no luck ☹


I have set my JAVA-HOME

[cid:image007.jpg@01D75B8C.DB6B9990]


What am I missing??

Thanks
Richard




Elsevier Limited. Registered Office: The Boulevard, Langford Lane, Kidlington, 
Oxford, OX5 1GB, United Kingdom, Registration No. 1982084, Registered in 
England and Wales.

Re: Unable to start NIFI

[Eduardo Fontes]

Hi Richard,

Do you tried to download the binary zip (not source)?
The basic installation is uncompress the binary zip and run bin/run-nifi.bat

Best regards.
Eduardo Fontes

On Mon, Jun 7, 2021 at 10:03 AM Honey, Richard (ELS-OXF) <
r.ho...@elsevier.com> wrote:

>
>
>
>
> Hi NIFI team
>
> I am struggling to understand what I have missed on implementing NIFI on
> my windows laptop?
>
>
>
> Same error every time -> *Could not find or load class
> org.apache.nifi.bootstrap.RunNiFi*
>
>
>
> I have installed both version just in case one has issue neither work
>
>
>
>
>
> Bin directory is in the depths of the folder
>
>
> nifi-1.12.1\nifi-1.12.1\nifi-nar-bundles\nifi-framework-bundle\nifi-framework\nifi-resources\src\main\resources\bin>
>
> Tried running bat as admin still no luck ☹
>
>
>
>
>
> I have set my JAVA-HOME
>
>
>
>
>
>
>
> What am I missing??
>
>
>
> Thanks
>
> Richard
>
>
>
> --
>
> Elsevier Limited. Registered Office: The Boulevard, Langford Lane,
> Kidlington, Oxford, OX5 1GB, United Kingdom, Registration No. 1982084,
> Registered in England and Wales.
>

Unable to start NIFI

[Honey, Richard (ELS-OXF)]

[cid:image002.jpg@01D75B8C.DB6B9990]


Hi NIFI team
I am struggling to understand what I have missed on implementing NIFI on my 
windows laptop?

Same error every time -> Could not find or load class 
org.apache.nifi.bootstrap.RunNiFi

I have installed both version just in case one has issue neither work

[cid:image006.jpg@01D75B8C.DB6B9990]

Bin directory is in the depths of the folder
nifi-1.12.1\nifi-1.12.1\nifi-nar-bundles\nifi-framework-bundle\nifi-framework\nifi-resources\src\main\resources\bin>
Tried running bat as admin still no luck ☹


I have set my JAVA-HOME

[cid:image007.jpg@01D75B8C.DB6B9990]


What am I missing??

Thanks
Richard




Elsevier Limited. Registered Office: The Boulevard, Langford Lane, Kidlington, 
Oxford, OX5 1GB, United Kingdom, Registration No. 1982084, Registered in 
England and Wales.

Unable to start NiFi when controller service references other controller services

[Mark Bean]

We are having issues when starting NiFi with a custom controller service
which allows dynamic properties. The dynamic properties are themselves
additional controller services. Enabling the custom controller service
after NiFi is running is fine. But, if the service is enabled on startup,
NiFi fails to start correctly and the UI is never presented.

When starting, as controller services are attempted to be enabled, they
first determine if there are referencing services required to be enabled
first. In the process of enabling each of these, the referenced controller
service is validated (so that its state can change from invalid to disabled
once all referencing services are enabled.)

However, the process never completes. It consistently stops at the exact
same point on each NiFi start attempt. The custom controller services
enables 6 of 19 referenced services, but fails on the 7th.

The thread enabling the controller service (created by
StandardControllerServiceNode) appears to simply stop.This occurs when
attempting to access the proxy controller service in
ControllerServiceDetails. I cannot explain why though.

Specific question: why does the thread hang when accessing the proxy
controller service?

General question: what purpose does the proxy controller service serve
versus the actual implementation?

Apache 1.10.0 (with patch applied for NIFI-6852)

Thanks,
Mark

Re: Unable to start NiFi

[Michael Moser]

Hello,

I see your VM arguments contain 2 "-Xms" and 0 "-Xmx" arguments:
   -Xms2048m -Xms2048m

Please check your nifi/conf/bootstrap.conf file to make sure the JVM memory
settings show
  -Xms2048m
  -Xmx2048m

Regards,
-- Mike



On Fri, Jan 19, 2018 at 6:25 AM, 尹文才  wrote:

> Hi guys, one of my colleagues was working on a remote deploy tool trying to
> start NiFi remotely on a windows system(NiFi package is on the windows
> system).
> I don't know how exactly the deployment tool works, but the basic flow is
> to launch Ansible locally which uses winrm to remotely
> launch NiFi through powershell. Unfortunately NiFi couldn't be started. But
> when he remotely logged into the windows system
> and manually ran NiFi on the system(through double clicking the
> run-nifi.bat file), NiFi started without any problem. I checked the logs
> written by NiFi about the start failure and it appears to me to be a memory
> problem, but I'm not sure if it is the root cause and don't know
> how to solve the problem. Could anyone help me out of this problem? Thanks.
> The 2 created logs are as below:
>
> 1. nifi-bootstrap.log:
> 2018-01-19 17:12:48,657 INFO [main] o.a.n.b.NotificationServiceManager
> Successfully loaded the following 0 services: []
> 2018-01-19 17:12:48,673 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STARTED
> 2018-01-19 17:12:48,673 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STOPPED
> 2018-01-19 17:12:48,673 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_DIED
> 2018-01-19 17:12:48,688 INFO [main] org.apache.nifi.bootstrap.Command
> Starting Apache NiFi...
> 2018-01-19 17:12:48,688 INFO [main] org.apache.nifi.bootstrap.Command
> Working Directory: C:\ETL\Nifi\NIFI-1~1.0
> 2018-01-19 17:12:48,688 INFO [main] org.apache.nifi.bootstrap.Command
> Command: C:\Program Files\Java\jdk1.8.0_152\bin\java.exe -classpath
> C:\ETL\Nifi\NIFI-1~1.0\.\conf;C:\ETL\Nifi\NIFI-1~1.0\.\lib\
> javax.servlet-api-3.1.0.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\
> jcl-over-slf4j-1.7.25.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\
> jetty-schemas-3.1.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\jul-to-
> slf4j-1.7.25.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\log4j-over-
> slf4j-1.7.25.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\logback-
> classic-1.2.3.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\logback-core-
> 1.2.3.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\nifi-api-1.4.0.jar;
> C:\ETL\Nifi\NIFI-1~1.0\.\lib\nifi-framework-api-1.4.0.jar;
> C:\ETL\Nifi\NIFI-1~1.0\.\lib\nifi-nar-utils-1.4.0.jar;C:\
> ETL\Nifi\NIFI-1~1.0\.\lib\nifi-properties-1.4.0.jar;C:\
> ETL\Nifi\NIFI-1~1.0\.\lib\nifi-runtime-1.4.0.jar;C:\ETL\
> Nifi\NIFI-1~1.0\.\lib\slf4j-api-1.7.25.jar
> -Dorg.apache.jasper.compiler.disablejsr199=true -Xms2048m -Xms2048m
> -Djava.security.egd=file:/dev/urandom
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
> -Djava.awt.headless=true -XX:+UseG1GC
> -Djava.protocol.handler.pkgs=sun.net.www.protocol
> -Dnifi.properties.file.path=C:\ETL\Nifi\NIFI-1~1.0\.\conf\nifi.properties
> -Dnifi.bootstrap.listen.port=49572 -Dapp=NiFi
> -Dorg.apache.nifi.bootstrap.config.log.dir=C:\ETL\Nifi\
> NIFI-1~1.0\bin\..\\..\logs
> org.apache.nifi.NiFi
> 2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
> #
> 2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
> # There is insufficient memory for the Java Runtime Environment to
> continue.
> 2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
> # Native memory allocation (mmap) failed to map 2147483648 bytes for Failed
> to commit area from 0x0006c000 to 0x00074000 of length
> 2147483648.
> 2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
> # An error report file with more information is saved as:
> 2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
> # C:\ETL\Nifi\NIFI-1~1.0\hs_err_pid3448.log
> 2018-01-19 17:12:49,657 ERROR [NiFi logging handler] org.apache.nifi.StdErr
> Picked up JAVA_TOOL_OPTIONS: "-Dfile.encoding=UTF8"
> 2018-01-19 17:12:49,657 ERROR [NiFi logging handler] org.apache.nifi.StdErr
> Java HotSpot(TM) 64-Bit Server VM warning: INFO:
> os::commit_memory(0x0006c000, 2147483648, 0) failed;
> error='ҳ���ļ�̫С���޷���ɲ�' (DOS error/errno=1455)
> 2018-01-19 17:12:50,876 WARN [main] org.apache.nifi.bootstrap.Command
> Failed to set permissions so that only the owner can read pid file
> C:\ETL\Nifi\NIFI-1~1.0\bin\..\run\nifi.pid; this may allows others to have
> access to the key needed to communicate with NiFi. Permissions should be
> changed so that only the owner can read this file
> 2018-01-19 17:12:53,816 WARN [main] org.apache.nifi.bootstrap.Command
> Failed to set permissions so that only the owner can read status file
> C:\ETL\Nifi\NIFI-1~1.0\bin\..\run\nifi.status; 

Unable to start NiFi

[尹文才]

Hi guys, one of my colleagues was working on a remote deploy tool trying to
start NiFi remotely on a windows system(NiFi package is on the windows
system).
I don't know how exactly the deployment tool works, but the basic flow is
to launch Ansible locally which uses winrm to remotely
launch NiFi through powershell. Unfortunately NiFi couldn't be started. But
when he remotely logged into the windows system
and manually ran NiFi on the system(through double clicking the
run-nifi.bat file), NiFi started without any problem. I checked the logs
written by NiFi about the start failure and it appears to me to be a memory
problem, but I'm not sure if it is the root cause and don't know
how to solve the problem. Could anyone help me out of this problem? Thanks.
The 2 created logs are as below:

1. nifi-bootstrap.log:
2018-01-19 17:12:48,657 INFO [main] o.a.n.b.NotificationServiceManager
Successfully loaded the following 0 services: []
2018-01-19 17:12:48,673 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STARTED
2018-01-19 17:12:48,673 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STOPPED
2018-01-19 17:12:48,673 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_DIED
2018-01-19 17:12:48,688 INFO [main] org.apache.nifi.bootstrap.Command
Starting Apache NiFi...
2018-01-19 17:12:48,688 INFO [main] org.apache.nifi.bootstrap.Command
Working Directory: C:\ETL\Nifi\NIFI-1~1.0
2018-01-19 17:12:48,688 INFO [main] org.apache.nifi.bootstrap.Command
Command: C:\Program Files\Java\jdk1.8.0_152\bin\java.exe -classpath
C:\ETL\Nifi\NIFI-1~1.0\.\conf;C:\ETL\Nifi\NIFI-1~1.0\.\lib\javax.servlet-api-3.1.0.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\jcl-over-slf4j-1.7.25.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\jetty-schemas-3.1.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\jul-to-slf4j-1.7.25.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\log4j-over-slf4j-1.7.25.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\logback-classic-1.2.3.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\logback-core-1.2.3.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\nifi-api-1.4.0.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\nifi-framework-api-1.4.0.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\nifi-nar-utils-1.4.0.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\nifi-properties-1.4.0.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\nifi-runtime-1.4.0.jar;C:\ETL\Nifi\NIFI-1~1.0\.\lib\slf4j-api-1.7.25.jar
-Dorg.apache.jasper.compiler.disablejsr199=true -Xms2048m -Xms2048m
-Djava.security.egd=file:/dev/urandom
-Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
-Djava.awt.headless=true -XX:+UseG1GC
-Djava.protocol.handler.pkgs=sun.net.www.protocol
-Dnifi.properties.file.path=C:\ETL\Nifi\NIFI-1~1.0\.\conf\nifi.properties
-Dnifi.bootstrap.listen.port=49572 -Dapp=NiFi
-Dorg.apache.nifi.bootstrap.config.log.dir=C:\ETL\Nifi\NIFI-1~1.0\bin\..\\..\logs
org.apache.nifi.NiFi
2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut #
2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
# There is insufficient memory for the Java Runtime Environment to continue.
2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
# Native memory allocation (mmap) failed to map 2147483648 bytes for Failed
to commit area from 0x0006c000 to 0x00074000 of length
2147483648.
2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
# An error report file with more information is saved as:
2018-01-19 17:12:49,657 INFO [NiFi logging handler] org.apache.nifi.StdOut
# C:\ETL\Nifi\NIFI-1~1.0\hs_err_pid3448.log
2018-01-19 17:12:49,657 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Picked up JAVA_TOOL_OPTIONS: "-Dfile.encoding=UTF8"
2018-01-19 17:12:49,657 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Java HotSpot(TM) 64-Bit Server VM warning: INFO:
os::commit_memory(0x0006c000, 2147483648, 0) failed;
error='ҳ���ļ�̫С���޷���ɲ�' (DOS error/errno=1455)
2018-01-19 17:12:50,876 WARN [main] org.apache.nifi.bootstrap.Command
Failed to set permissions so that only the owner can read pid file
C:\ETL\Nifi\NIFI-1~1.0\bin\..\run\nifi.pid; this may allows others to have
access to the key needed to communicate with NiFi. Permissions should be
changed so that only the owner can read this file
2018-01-19 17:12:53,816 WARN [main] org.apache.nifi.bootstrap.Command
Failed to set permissions so that only the owner can read status file
C:\ETL\Nifi\NIFI-1~1.0\bin\..\run\nifi.status; this may allows others to
have access to the key needed to communicate with NiFi. Permissions should
be changed so that only the owner can read this file
2018-01-19 17:12:55,798 INFO [main] org.apache.nifi.bootstrap.Command
Launched Apache NiFi with Process ID 3448
2018-01-19 17:12:55,798 INFO [main] org.apache.nifi.bootstrap.RunNiFi NiFi
never started. Will not restart NiFi


2. hs_err_pid3448.log:

#
# There is insufficient memory for the Java Runtime Environment