Hi André, It works, however I'm still facing problems to start the MiNiFi, now I'm seeing the following errors in the nifi-app.log 2022-04-02 17:25:56,124 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 22, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,140 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 75, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,140 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 126, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,140 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 177, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 212, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 242, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 277, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 359, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 407, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 446, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,171 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 486, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,171 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 549, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,171 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 612, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,191 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 680, col 28: cvc-complex-type.2.4.a: Invalid content was found starting with element 'networkInterface'. One of '{inputPort, outputPort}' is expected.
2022-04-02 17:25:56,311 INFO [main] o.a.nifi.headless.HeadlessNiFiServer Loading Flow...
2022-04-02 17:25:56,343 WARN [main] o.a.nifi.headless.HeadlessNiFiServer Failed to start headless server... shutting down.
java.lang.Exception: Unable to load flow due to: java.lang.IllegalArgumentException: NiFi Sensitive Properties Key [nifi.sensitive.props.key] is required
at org.apache.nifi.headless.HeadlessNiFiServer.start(HeadlessNiFiServer.java:166)
at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:163)
at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:64)
at org.apache.nifi.minifi.MiNiFi.main(MiNiFi.java:265)
Caused by: java.lang.IllegalArgumentException: NiFi Sensitive Properties Key [nifi.sensitive.props.key] is required
at org.apache.nifi.encrypt.PropertyEncryptorFactory.getPropertyEncryptor(PropertyEncryptorFactory.java:42)
at org.apache.nifi.headless.HeadlessNiFiServer.start(HeadlessNiFiServer.java:125)
... 3 common frames omitted
2022-04-02 17:25:56,343 INFO [Thread-1] org.apache.nifi.minifi.MiNiFi Initiating shutdown of MiNiFi server...
2022-04-02 17:25:56,343 WARN [Thread-1] o.a.nifi.headless.HeadlessNiFiServer Problem occurred ensuring flow controller or repository was properly terminated due to java.lang.NullPointerException
2022-04-02 17:25:56,343 ERROR [Thread-1] org.apache.nifi.BootstrapListener Failed to communicate with Bootstrap. Bootstrap may be unable to issue or receive commands from MiNiFi
2022-04-02 17:25:56,343 INFO [Thread-1] org.apache.nifi.minifi.MiNiFi MiNiFi server shutdown completed (nicely or otherwise). About the warnings I could not find which processors in the flow has the maxconcurrentask unset, all have one as value (1). About the network interface, input and output ports warnings I suppose that it refers to the remote process group. In this point, I understand that, at least the network interface, is an optional parameter. The final error, nifi.sensitive.props.key. I seted this property but when minifi try to starts set the value to empty again and then fails. Thanks again.
... View more
