[
https://issues.apache.org/jira/browse/NIFI-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552955#comment-17552955
]
Mogana Richards commented on NIFI-10048:
----------------------------------------
i was able to recreate this issue. If you run set-sensitive-properties-key to
add a password and your flow.xml.gz is not available at that time you get into
a weird inconsistent state where you have nifi.properties updated with a
password and flow.xml.gz not encrypted with the password. It does not throw the
normal error pad block corrupted. Also, removing the flow file from conf and
expecting it to pull down one from the cluster does not work. To resolve, I
copied the flow.xml.gz that i had backed up prior to upgrade back to conf,
removed the sensitive keys property and reranset-sensitive-properties-key, then
started nifi.
> Apache Nifi Web Server keeps failing to start
> ----------------------------------------------
>
> Key: NIFI-10048
> URL: https://issues.apache.org/jira/browse/NIFI-10048
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.16.1
> Reporter: Andreas Adamides
> Priority: Critical
>
> The following exception keeps occurring on the Apache NiFi Cluster, this is
> from the app logs:
> {code:java}
> 2022-05-24 15:13:03,669 INFO [main] o.a.n.c.s.VersionedFlowSynchronizer
> Synching FlowController with proposed flow: Controller Already Synchronized =
> false
> 2022-05-24 15:13:04,260 WARN [main] org.apache.nifi.web.server.JettyServer
> Failed to start web server... shutting down.
> java.lang.NullPointerException: null
> at
> org.apache.nifi.registry.flow.diff.StandardFlowDifference.hashCode(StandardFlowDifference.java:92)
> at java.util.HashMap.hash(HashMap.java:340)
> at java.util.HashMap.put(HashMap.java:613)
> at java.util.HashSet.add(HashSet.java:220)
> at
> org.apache.nifi.registry.flow.diff.StandardFlowComparator.addIfDifferent(StandardFlowComparator.java:562)
> at
> org.apache.nifi.registry.flow.diff.StandardFlowComparator.compare(StandardFlowComparator.java:447)
> at
> org.apache.nifi.registry.flow.diff.StandardFlowComparator.compare(StandardFlowComparator.java:92)
> at
> org.apache.nifi.registry.flow.diff.StandardFlowComparator.compare(StandardFlowComparator.java:77)
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.compareFlows(VersionedFlowSynchronizer.java:383)
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:165)
> at
> org.apache.nifi.controller.serialization.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:43)
> at
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1524)
> at
> org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:104)
> at
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:815)
> at
> org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:457)
> at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1086)
> at org.apache.nifi.NiFi.<init>(NiFi.java:170)
> at org.apache.nifi.NiFi.<init>(NiFi.java:82)
> at org.apache.nifi.NiFi.main(NiFi.java:330)
> 2022-05-24 15:13:04,261 INFO [Thread-1] org.apache.nifi.NiFi Application
> Server shutdown started{code}
> There is not a Nifi Registry in the setup, I have tried to tear everything
> down to freshly install Nifi Cluster, but it keeps failing to start. This has
> been part of a helm chart/k8 setup. This issue occurs in 2 nodes of a 3-node
> Nifi cluster. I manage to fix it when downgrading to 1 node overall, which
> does not make a lot of sense.
>
> Can anyone suggest what I am doing wrong?
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
