Member since
03-11-2022
30
Posts
11
Kudos Received
3
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1841 | 03-26-2024 07:33 AM | |
| 22953 | 01-22-2024 06:12 AM | |
| 1579 | 01-12-2024 08:59 AM |
03-26-2024
03:27 AM
1 Kudo
Hi there, Maybe some one can help us out. Searching on the web for similar error's doesn't give us a lead on what is going on. Let me sketch out what is happening. Last week we were cleaning up some old buckets with flows from the nifi-registry manually thru the web gui. At some point we received an error that pointed us the registry logs. Actually didn't see anything there. To test if everything is still working, we tried to commit a change to a versioned flow. Which failed. Unfortunately I don't have the error anymore. So decided to restart the registry hoping that this will help. And now it has gotten worse, the registry isn't starting anymore and is showing the error below. 2024-03-26 09:40:28,551 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getFlowPersistenceProvider' defined in class path resource [org/apache/nifi/registry/provider/StandardProviderFactory.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apache.nifi.registry.flow.FlowPersistenceProvider]: Factory method 'getFlowPersistenceProvider' threw exception; nested exception is java.lang.NullPointerException What is this error trying to tell us? This is our provider config: <flowPersistenceProvider> <class>org.apache.nifi.registry.provider.flow.git.GitFlowPersistenceProvider</class> <property name="Flow Storage Directory">./flow_storage</property> <property name="Remote To Push">origin</property> <property name="Remote Access User"></property> <property name="Remote Access Password"></property> </flowPersistenceProvider> Any help would be much appreciated. Thank you in advanced. Kind regards, Dave
... View more
Labels:
- Labels:
-
NiFi Registry
03-20-2024
08:17 AM
Hi there @mburgess thank you for your reply. Let play around with your solution and see if i can get it working and write the output to a flowfile 🤓
... View more
03-13-2024
06:03 AM
1 Kudo
Hi there , We are looking for a way to list all keys of redis cache thru nifi. The best solution we found was a groovy script from this article Get list of keys in NiFi DistributedMapCache The script looks good and exactly what we are looking for. But when we try to implement it, we get the following error: We are using the invokescriptprocessor and configure like this What are we missing here 😉 Or another solutions is also more than welcome. Thank you in advanced. Kind regards, Dave
... View more
Labels:
- Labels:
-
Apache NiFi
03-13-2024
05:57 AM
1 Kudo
Hi Diana, good idea. I'll create a new thread. Thank you.
... View more
03-13-2024
04:06 AM
1 Kudo
Hi there, the script looks good and exactly what we are looking for. Just a quick question, when we try to implement it, we get the following error: We are using the invokescriptprocessor and configure like this What are we missing here 😉 Thank you.
... View more
01-22-2024
06:12 AM
1 Kudo
Above registry issue also solve, with the help of this thread 🤓 https://community.cloudera.com/t5/Support-Questions/NIfi-and-Nifi-Registry-Integration/m-p/286469
... View more
01-22-2024
04:19 AM
Hi Mat, it works! Awesome, nifi 1.24 starts up with the flow we had from 1.13 👏 Thank you very much for the advice. We are again one step further towards finalizing our migration plan. Only thing left is is now we get the following error from the flow with regards to the nifi-registry. Jan 22 10:57:46 awsinstancename docker[19956]: 2024-01-22 10:57:45,991 ERROR [Timer-Driven Process Thread-4] o.a.nifi.groups.StandardProcessGroup Failed to synchronize StandardProcessGroup[identifier=9311b848-f003-3b2a-ab11-af9e8884bc89,name=CheckScratchPrijs] with Flow Registry because could not retrieve version 7 of flow with identifier ab161029-c69f-4cf2-b6b3-12f444896e3e in bucket 3be9f87e-3a97-400c-a174-f335de21f23a Jan 22 10:57:46 awsinstancename docker[19956]: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.SSLHandshake.consume(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.TransportContext.dispatch(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) Jan 22 10:57:46 awsinstancename docker[19956]: at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) I'll open een separate thread for this
... View more
01-21-2024
11:28 PM
1 Kudo
Thank you very much Mat for your advice. I'll try it out today and get back to you with the results. Sounds promising 🤓
... View more
01-19-2024
07:51 AM
1 Kudo
After some trial and errors found where the problem lies, our nifi 1.13 uses the old alogrithm: PBEWITHMD5AND256BITAES-CBC-OPENSSL I tried to change this running the following command to change the flow.xml.gz and flow.json.gz to the correct algo. # ./nifi.sh set-sensitive-properties-algorithm NIFI_PBKDF2_AES_GCM_256 Java home: /opt/java/openjdk NiFi home: /opt/nifi/nifi-current Bootstrap Config File: /opt/nifi/nifi-current/conf/bootstrap.conf Failed to process Flow Configuration [/nifi-data/conf/flow.xml.gz] org.apache.nifi.encrypt.EncryptionException: Decryption Failed with Algorithm [AES/GCM/NoPadding] at org.apache.nifi.encrypt.CipherPropertyEncryptor.decrypt(CipherPropertyEncryptor.java:78) at org.apache.nifi.flow.encryptor.AbstractFlowEncryptor.getOutputEncrypted(AbstractFlowEncryptor.java:31) at org.apache.nifi.flow.encryptor.XmlFlowEncryptor.processFlow(XmlFlowEncryptor.java:57) at org.apache.nifi.flow.encryptor.StandardFlowEncryptor.processFlow(StandardFlowEncryptor.java:50) at org.apache.nifi.flow.encryptor.command.FlowEncryptorCommand.processFlowConfiguration(FlowEncryptorCommand.java:135) at org.apache.nifi.flow.encryptor.command.FlowEncryptorCommand.processFlowConfigurationFiles(FlowEncryptorCommand.java:119) at org.apache.nifi.flow.encryptor.command.FlowEncryptorCommand.run(FlowEncryptorCommand.java:96) at org.apache.nifi.flow.encryptor.command.SetSensitivePropertiesAlgorithm.main(SetSensitivePropertiesAlgorithm.java:29) Caused by: javax.crypto.AEADBadTagException: Tag mismatch! at java.base/com.sun.crypto.provider.GaloisCounterMode.decryptFinal(Unknown Source) at java.base/com.sun.crypto.provider.CipherCore.finalNoPadding(Unknown Source) at java.base/com.sun.crypto.provider.CipherCore.fillOutputBuffer(Unknown Source) at java.base/com.sun.crypto.provider.CipherCore.doFinal(Unknown Source) at java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(Unknown Source) at java.base/javax.crypto.Cipher.doFinal(Unknown Source) at org.apache.nifi.encrypt.CipherPropertyEncryptor.decrypt(CipherPropertyEncryptor.java:74) ... 7 more NiFi Properties Processed [/opt/nifi/nifi-current/conf/nifi.properties] So i know here it's failing, but no solution yet.
... View more
01-18-2024
11:34 PM
Hi there, I need some help regarding using a flow.xml.gz from 1.13 to 1.24. First our nifi setup: 2 node cluster running on ec2 instances in aws where we run nifi in docker containers. We have succesfully upgraded from 1.13 to 1.24 after making a backup of the flow.xml.gz file. We then stop the nifi containers and put back the flow.xml.gz from version 1.13. Then startup nifi. Unfortunately we get the following error: Jan 19 07:20:58 nifi-node-1 docker[27934]: 2024-01-19 07:20:58,216 INFO [main] org.eclipse.jetty.server.Server Started @78240ms Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:58,304 INFO [main] org.apache.nifi.web.server.JettyServer Loading Flow... Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:58,326 INFO [main] o.apache.nifi.io.socket.SocketListener Now listening for connections from nodes on port 8888 Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,036 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 10, col 20: cvc-complex-type.2.4.b: The content of element 'flowRegistry' is not complete. One of '{class}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,037 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 16, col 20: cvc-complex-type.2.4.b: The content of element 'flowRegistry' is not complete. One of '{class}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,037 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 27, col 16: cvc-complex-type.2.4.a: Invalid content was found starting with element 'value'. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,037 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 33, col 16: cvc-complex-type.2.4.a: Invalid content was found starting with element 'value'. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,045 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 39, col 16: cvc-complex-type.2.4.a: Invalid content was found starting with element 'value'. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,045 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 45, col 19: cvc-complex-type.2.4.b: The content of element 'parameter' is not complete. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,046 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 50, col 16: cvc-complex-type.2.4.a: Invalid content was found starting with element 'value'. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,046 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 56, col 19: cvc-complex-type.2.4.b: The content of element 'parameter' is not complete. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,046 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 61, col 16: cvc-complex-type.2.4.a: Invalid content was found starting with element 'value'. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,047 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 67, col 19: cvc-complex-type.2.4.b: The content of element 'parameter' is not complete. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,047 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 72, col 16: cvc-complex-type.2.4.a: Invalid content was found starting with element 'value'. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,047 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 78, col 16: cvc-complex-type.2.4.a: Invalid content was found starting with element 'value'. One of '{provided}' is expected. Jan 19 07:20:59 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,048 WARN [main] o.a.nifi.fingerprint.FingerprintFactory Schema validation error parsing Flow Configuration at line 84, col 16: cvc-complex-type.2.4.a: Invalid content was found starting with element 'value'. One of '{provided}' is expected. Jan 19 07:21:00 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,703 WARN [main] org.apache.nifi.web.server.JettyServer Failed to start web server... shutting down. Jan 19 07:21:00 nifi-node-1 docker[27934]: org.apache.nifi.encrypt.EncryptionException: Decryption Failed with Algorithm [AES/GCM/NoPadding] Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.encrypt.CipherPropertyEncryptor.decrypt(CipherPropertyEncryptor.java:78) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.fingerprint.FingerprintFactory.decrypt(FingerprintFactory.java:996) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.fingerprint.FingerprintFactory.getLoggableRepresentationOfSensitiveValue(FingerprintFactory.java:605) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.fingerprint.FingerprintFactory.addParameter(FingerprintFactory.java:360) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.fingerprint.FingerprintFactory.addParameterContext(FingerprintFactory.java:326) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.fingerprint.FingerprintFactory.addFlowControllerFingerprint(FingerprintFactory.java:219) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.fingerprint.FingerprintFactory.createFingerprint(FingerprintFactory.java:155) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.fingerprint.FingerprintFactory.createFingerprint(FingerprintFactory.java:129) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.controller.inheritance.FlowFingerprintCheck.checkInheritability(FlowFingerprintCheck.java:45) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.controller.XmlFlowSynchronizer.sync(XmlFlowSynchronizer.java:205) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.controller.serialization.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:42) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1530) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:104) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:817) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:457) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:896) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.NiFi.<init>(NiFi.java:172) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.NiFi.<init>(NiFi.java:83) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.NiFi.main(NiFi.java:332) Jan 19 07:21:00 nifi-node-1 docker[27934]: Caused by: javax.crypto.AEADBadTagException: Tag mismatch! Jan 19 07:21:00 nifi-node-1 docker[27934]: at java.base/com.sun.crypto.provider.GaloisCounterMode.decryptFinal(Unknown Source) Jan 19 07:21:00 nifi-node-1 docker[27934]: at java.base/com.sun.crypto.provider.CipherCore.finalNoPadding(Unknown Source) Jan 19 07:21:00 nifi-node-1 docker[27934]: at java.base/com.sun.crypto.provider.CipherCore.fillOutputBuffer(Unknown Source) Jan 19 07:21:00 nifi-node-1 docker[27934]: at java.base/com.sun.crypto.provider.CipherCore.doFinal(Unknown Source) Jan 19 07:21:00 nifi-node-1 docker[27934]: at java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(Unknown Source) Jan 19 07:21:00 nifi-node-1 docker[27934]: at java.base/javax.crypto.Cipher.doFinal(Unknown Source) Jan 19 07:21:00 nifi-node-1 docker[27934]: at org.apache.nifi.encrypt.CipherPropertyEncryptor.decrypt(CipherPropertyEncryptor.java:74) Jan 19 07:21:00 nifi-node-1 docker[27934]: ... 18 common frames omitted Jan 19 07:21:00 nifi-node-1 docker[27934]: 2024-01-19 07:20:59,733 INFO [Thread-0] org.apache.nifi.NiFi Application Server shutdown started Any help would be much appreciated. Thank you. Greetz Dave
... View more
Labels:
- Labels:
-
Apache NiFi
- « Previous
-
- 1
- 2
- Next »