hello in the logs above I don't see any log which describes LogAttribute (the screenshot you have posted above says it is a LogAttribute processor) being started or stopped. Also anyway to know which user did this ... View more

Hello @LaurisG_,  Hope you are doing fine.  I think this one is also related to the CM version you have, as mentioned on: https://community.cloudera.com/t5/Support-Questions/Ranger-UserSync-and-RMS-fails-after-upgrade-7-1-9-7-3-2-0-GA/td-p/414110 As this is unsupported it may send wrong settings to the services.  Can you try upgrading the CM and see if the Atlas service starts properly? ... View more

Hello @LaurisG_,  Thanks for being part of our community.  I was reading through the issue and found a similar issue reported before. The issue was an unsupported Cloudera Manager used for the Runtime.  And in your scenario, this is happening too.  You mentioned you have Cloudera Manager 7.11.3, but this version does not support Cloudera Runtime 7.3.2.  That could cause the issue you're seeing.  You should be using Cloudera Manager 7.13.2, as that is the supported version for your Runtime.  https://docs.cloudera.com/cdp-private-cloud-base/7.3.2/cdp-private-cloud-base-installation/topics/cm-cdh-compatibility.html  https://supportmatrix.cloudera.com/  Try upgrading the CM and then retry the Role start.  ... View more

@nisaar  I agree with @vafs  that sharing the completed ERROR and stack trace is always gong to be most helpful in your community questions.  Those full stack traces will have classes like "net.schmizz.sshj.transport" that you could try putting in to DEBUG within the NiFi logback to see what additional logging that class (not a NiFi library, but used by NiFi) may provide.  Matt ... View more

@Dagonvlg 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

Hi @dylee  Welcome to cloudera community! just wanted add some more details to @vafs response: you are encountering at https://archive.cloudera.com/cdp-public/ is expected behavior. Cloudera has changed how its repositories are structured and accessed, particularly for CDP (Cloudera Data Platform). The path cdp-public is not a browsable directory. To verify access and proceed with your trial installation, please refer to the following details regarding the repository structure and authentication: 1. The Repository Path has Changed For modern CDP installations, Cloudera often uses a different path structure. If you are looking for Cloudera Manager or Runtime artifacts, the URLs typically include a /p/ (private/protected) or a specific version prefix. Example for Cloudera Manager 7: https://archive.cloudera.com/p/cm7/ Example for Runtime: https://archive.cloudera.com/p/cdh7/ (Note that CDP Private Cloud Base artifacts are often under the cdh7 path). 2. Authentication Requirements (The "Paywall") Since February 2021, Cloudera moved its software behind a paywall. Even for trial environments, you generally cannot access the repositories without valid credentials. Trial Credentials: When you signed up for the CDP trial, you should have received a License Key or a set of Remote Repository Credentials (username/password). Verification: You cannot "browse" the root of the archive in a browser to verify access. Instead, you must test a specific file download using your trial credentials. If you do not have credentials, you can request them via the Cloudera Trial Portal or contact your Cloudera Account Manager. Test Command: curl -u <your_username>:<your_password> https://archive.cloudera.com/p/cm7/7.x.x/allkeys.asc If your issue has been resolved, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. ... View more

Hi, I had to downgrade and upgrade all my nars to 2.0.0 for it to work. ... View more

Thank you André, This led to the right direction. Since the configuration file is required by a third party JAR that I don't build, the way to solve it was to add a src/main/resources path to the myProcessor-nar directory instead of the myProcessor-processor directory. The nar directory doesn't include a src/main/java but you can nevertheless add a src/main/resources path and add subfolders/files to it, e.g. NAR-INF/data/config.ini. Maven will copy automatically everything under src/main/resources to the target, hence it's not necessary to add the resources snippet to the pom.xml. So, now NiFi's work/nar/extensions/myProcessor-nar-1.0.nar-unpacked/NAR-INF folder contains my subfolder/file data/config.ini every time NiFi unpacks the NAR. I found this article helpful that explains the parts of a NAR and the three pom.xml files: https://www.javahotchocolate.com/notes/nifi-project.html Thanks @vafs! ... View more