@Nick,   Thanks for the log.  Unfortunately, it does not contain information regarding the stop or start activity that might have led to this condition.   Currently, the supervisor and agent seem to be in an "invalid" state that is not handled by the agent code.   I would recommend restarting the agent on one host and see if that helps prevent the error from occurring. Run:   systemctl restart cloudera-scm-agent   Monitor the agent logs on the host where you restarted the agent to see if there are any errors.   If that doesn't help, we may need to restart the supervisor as well...  Let us know. ... View more

@TCloud,   Can you clarify the problem you are seeing regarding port 7182? ... View more

I tested on CM 6.2 and did not encounter the problem on CFM 1.0.1.0. My process directory (created by CM/agent for the process to start) does not include the file. However, the config.zip that is in the process directory does contain it:   [root@host-10-17-100-225 2537-nifitoolkitca-NIFI_TOOLKIT_SERVER]# unzip -l config.zip Archive: config.zip Length Date Time Name --------- ---------- ----- ---- 2094 07-13-2019 13:44 staging/globals.xml 1192 07-13-2019 13:44 logback.xml 828 07-13-2019 13:44 scripts/cc.sh 294 07-13-2019 13:44 cloudera-monitor.properties 238 07-13-2019 13:44 aux/configbuilder/ca-config.json 0 07-13-2019 13:44 redaction-rules.json 308 07-13-2019 13:44 cloudera-stack-monitor.properties 1205 07-13-2019 13:44 aux/templates/env.sh 1280 07-13-2019 13:44 aux/templates/config.json 989 07-13-2019 13:44 aux/templates/hadoop_xml_properties.j2 2332 07-13-2019 13:44 scripts/control.sh 1006 07-13-2019 13:44 aux/configbuilder/control-env.json 809 07-13-2019 13:44 aux/defaults/nifi-ca-client.xml   I saw one hint in an internal discussion that permissions on /var/lib/nifi* could be an issue... can you do an "ls -lrt /var/lib/nifi*" and show the results?   I'll work with the NiFi team on Monday to see if we can get this working for you. ... View more

@anung @Sheldon_G @Nando ,   I'm sorry to hear you are hitting this issue.  Let me walk through the install and see if I can lend a hand.  What instructions are you using?  ... View more

Hi @TCloud ,   The documentation contains information about the trusstore in Step 4: https://www.cloudera.com/documentation/enterprise/latest/topics/how_to_configure_cm_tls.html#concept_xtp_q3w_wn   It does not include *what* to put in the truststore file, though, so yes, that is something that should be improved.   If you are using a Certificate Authority to sign your certificates, you can simply add the root CA certificate to the truststore. If you are using self-signed certificates, each agent's certificate needs to be imported so CM can validate the agent's certificate.     ... View more

@ca,   Testing for compliance and compatibilty takes a good deal of effort so we usually only certifiy later OS release on the latest CM/CDH versions.   By "supported" in this case we mean that we have tested and certify CM/CDH on that OS release.   Part of obtaining software from our distrobution is that we test to help ensure stability with the products.  That takes some of the guess-work out, but that also means that if you want that assurance, "certified" configurations may not include the latest OS releases and third-party code. We seek to balance stability with rich features that our users demand.   Hope that helps explain things a bit more.  Please feel free to ask more if you have any questions! ... View more