Member since
11-17-2021
1116
Posts
253
Kudos Received
28
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 224 | 10-16-2025 02:45 PM | |
| 473 | 10-06-2025 01:01 PM | |
| 442 | 09-24-2025 01:51 PM | |
| 399 | 08-04-2025 04:17 PM | |
| 480 | 06-03-2025 11:02 AM |
02-07-2025
05:48 AM
@Darryl Please start a new community question around your new keycloak integration issues with NiFi. Thank you, Matt
... View more
02-03-2025
11:43 AM
@AbhiTryingAgain Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
02-03-2025
11:40 AM
@ose_gold Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
02-03-2025
06:24 AM
@Shampy You are saying that with no flow.json.gz file present, NIFi throws above exception on startup. With No flow.json.gz file, NiFi will create one during startup. I also suggest using the official Apache NiFi 2.x release and stop using the pre-release Maintenance releases that were put out during development of NiFi 2.x. There were 4 maintenance (M1 - M4) releases put out before the first official release of Apache NiFi 2.0.0. The latest official release ofd Apache NiFi 2.x is NiFi 2.2.0 which can be downloaded from here: https://nifi.apache.org/download/ Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt
... View more
01-31-2025
04:29 AM
Based on the initial input in the question, slightly adapted the following seems to work for me (1.27.0) docker run --rm --name nifi -p 8080:8080 \ -e NIFI_WEB_HTTP_PORT=8080 \ -e NIFI_WEB_HTTPS_PORT= \ -e NIFI_WEB_HTTPS_HOST= \ -e NIFI_SECURITY_KEYSTORE= \ -e NIFI_SECURITY_KEYSTOREPASSWD= \ -e NIFI_SECURITY_KEYPASSWD= \ -e NIFI_SECURITY_TRUSTSTORE= \ -e NIFI_SECURITY_TRUSTSTOREPASSWD= \ apache/nifi:1.27.0 --- --- from container nifi@xxxxxxxxxxxx:/opt/nifi/nifi-toolkit-current/bin$ ./cli.sh _ ___ _ Apache (_) .' ..](_) , _ .--. __ _| |_ __ )\ [ `.-. | [ |'-| |-'[ | / \ | | | | | | | | | | ' ' [___||__][___][___] [___]', ,' `' CLI v1.27.0 Type 'help' to see a list of available commands, use tab to auto-complete. Session loaded from /home/nifi/.nifi-cli.config #> nifi get-root-id xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
... View more
01-29-2025
05:57 AM
Are there any updates on this? I'm experiencing the same issue
... View more
01-28-2025
09:19 AM
Thank You for checking it out! I have just questions about terminology: - what do U mean by "workspace"? Is it an Cloudera environment we can find in Management Console? - "suspended the workspace" means stop environment?
... View more
01-28-2025
08:00 AM
@enguias Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
01-25-2025
01:42 AM
1 Kudo
I found a solution for this trouble. I removed kerberos DB with kdb5-util destroy and I recreate it again kdb5-util create -s. Other thing what I found was that, when I firstly created admin cloudera principal I used cloudera-scm instead of cloudera-scm/admin. I am not sure if this could caused problem, but after destroying old DB and created cloudera-scm/admin, generating is working properly.
... View more