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 @AlokKumar,  Thanks for being part of the community.  Yes, that is possible.  You should be able to search on the nifi-user.log for entries. You can either filter them by user or by processor IDs.  For example, I did some starts and stops for this processor.  By checking the log using the ID, I found this:  2026-05-26 18:29:40,582 INFO [NiFi Web Server-36464] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status 2026-05-26 18:29:40,582 INFO [NiFi Web Server-36464] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status 2026-05-26 18:29:40,597 INFO [NiFi Web Server-33000] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status 2026-05-26 18:29:40,598 INFO [NiFi Web Server-33000] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status ... 2026-05-26 18:29:51,454 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status 2026-05-26 18:29:51,455 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status 2026-05-26 18:29:51,465 INFO [NiFi Web Server-36510] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status 2026-05-26 18:29:51,465 INFO [NiFi Web Server-36510] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status Also, by checking the ID for a proccessor group I see the following:  2026-05-26 18:31:40,166 INFO [NiFi Web Server-36460] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/process-groups/658e5692-019e-1000-ffff-ffff8f55b0de 2026-05-26 18:31:40,167 INFO [NiFi Web Server-36460] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/process-groups/658e5692-019e-1000-ffff-ffff8f55b0de 2026-05-26 18:31:40,187 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/process-groups/658e5692-019e-1000-ffff-ffff8f55b0de 2026-05-26 18:31:40,188 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/process-groups/658e5692-019e-1000-ffff-ffff8f55b0de This should give you the information you want.  ... 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

Hello @nisaar,  sftp CLI and PutSFTP can internally work differently.  Have you check nifi-app.log from the NiFi nodes to review the error?  If so, can you share here the message to take a look.  ... View more

Hello @Dagonvlg,  The best option should be on NiFi UI, in that way you can execute it as stateless:  https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-stateless-processor-nar/1.28.0/org.apache.nifi.processors.stateless.ExecuteStateless/index.html  ... View more

Hello @Dagonvlg,  As far as I know, NiFi 2 does not have a stateless mode to the entire service.  That was removed.  But what it offers is an stateless engine. You can configure it at Processor Group level:  https://nifi.apache.org/nifi-docs/user-guide.html#stateless-execution-engine  ... View more

Hello @dylee,  Try with https://archive.cloudera.com/p/cdp-public/ this one do open and have all the available versions.  ... View more

Hello @MusabAlosaimi,  I would suggest to open an administrative case on Lighthouse.  They could help you updating your profile.  ... View more

Hello @YSFSK,  I understand now. I do see the error you mention:  2026-04-02 12:22:09,133 INFO [MiNiFi logging handler] org.apache.nifi.minifi.StdOut 12:22:09.133 [pool-15-thread-1] DEBUG org.apache.nifi.controller.serialization.VersionedFlowSynchronizer -- Could not find a compatible bundle for org.apache.nifi:nifi-azure-nar:2.4.0 type org.apache.nifi.processors.azure.eventhub.PutAzureEventHub That error points to be a problem with the version.  So we are basically on the same point.  We have nifi-azure-nar at 2.4.0, nifi-azure-services-api at 2.3.0 and nifi-cdf-debezium-postgresql at 1.28.1.  This is a mix that is not working. I do not know the NiFi version you have, but should use that version for all the NARs as well. Using different versions is not a good idea.  You can download them from the Sonatype Nexus Repository.  ... View more