Ok for future users 🙂 Check if certyficate is generated by ambari server from one of the nodes: openssl s_client -connect server_address:8440 corect results (similar): ---Server certificate-----BEGIN CERTIFICATE----- MIIFnDCCA4SgAwIBAgIBATANBgkqhkiG9w0BAQsFADBCMQswCQYDVQQGEwJYWDEV ................. ................. If you are not receiving corect handshake you need to verify ambari-server.ini (ambari server): vi /etc/ambari-server/conf/ambari.properties and # the line with TLS cyphers 🙂 , Ok for future users 🙂 Check if certyficate is generated by ambari server from one of the nodes: openssl s_client -connect server_address:8440 corect results (similar): ---Server certificate-----BEGIN CERTIFICATE----- MIIFnDCCA4SgAwIBAgIBATANBgkqhkiG9w0BAQsFADBCMQswCQYDVQQGEwJYWDEV ................. ................. If you are not receiving corect handshake you need to verify ambari-server.ini (ambari server): vi /etc/ambari-server/conf/ambari.properties and # the line with TLS cyphers 🙂 ... View more

Thanks a lot! It worked. ... View more

The issue was that the reverse dns was not correctly configured and adding all the hosts to /etc/hosts made it work. I still wonder why this was working before the stop, wait one week, start of the cluster VMs. A cache that was hiding the problem ? ... View more

Thanks for the wonderful article! Have one question. When we export a flow/component as template, all the sensitive values in the processors gets cleared out even when they are set as EL and not actual values. This makes it hard for to auto deploy Nifi pipelines pulling the templates from a Git repo and deploying on to Nifi without manual intervention. Is there any suggestions for a Nifi SDLC that will handle processors with sensitive properties. So far I have been to get it almost working, by using external custom properties and the Nifi REST API for deploying and instantiating templates. But the sensitive values getting clearing out in the template would manual population of the sensitive properties. ... View more