@ecampos  To resolve this issue and to allow CM server to start, modify the db.properties file as below:  Note: Back up the current file at /etc/cloudera-scm-server/db.properties. --------------- com.cloudera.cmf.db.type = mysql com.cloudera.cmf.orm.hibernate.connection.url=jdbc:mysql://<db_host>/scm?allowPublicKeyRetrieval=true&useSSL=false com.cloudera.cmf.orm.hibernate.connection.username=scm com.cloudera.cmf.orm.hibernate.connection.password=cloudera com.cloudera.cmf.db.setupType=EXTERNAL --------------- ... View more

To disable Kerberos in Cloudera, it’s important to know that there is no direct option to turn it off entirely once enabled, as Kerberos is typically applied cluster-wide. It's generally not recommended to disable Kerberos once enabled due to security implications. ... View more

Firstly, it is essential to determine the cause of the permissions change. Some possible factors could be a misconfigured script or process running on the server, a security setting, or interaction with other components of your system. To troubleshoot this issue, you could start by checking your system logs (/var/log/syslog or similar) and any relevant application logs for any hints about what is causing the permissions change. Additionally, you may want to review any configuration files or scripts that might be involved in managing the permissions of the /var/log directory. Since you mentioned that SELinux is disabled and the firewall is also disabled, it is less likely that these factors are causing the problem. However, I would recommend double-checking any remaining security settings or access control policies that could potentially impact the /var/log directory. As a temporary workaround, you mentioned using a crontab that changes the permissions of the directory to 755 every 5 minutes. While this may alleviate the issue temporarily, it is not a sustainable solution in the long run. Instead, it would be more ideal to identify and address the root cause of the permissions change. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. ... View more

Based on the provided information, it seems that you are able to successfully log in to Nifi, but you are encountering an error when trying to access the Nifi UI. The error message suggests that there is an SSLPeerUnverifiedException, specifically related to the hostname and subjectAltNames. This error usually occurs when there is a certificate validation issue. The certificate being used by Nifi may not be recognized or trusted by your system, causing the SSL connection to fail. To resolve this issue, you can try the following steps: 1. Check the certificate: Verify the certificate being used by Nifi and ensure it is correctly configured. Make sure that the certificate has the correct subjectAltName entries for the hostname you are using to access Nifi UI. 2. Trust the certificate: If the certificate is valid but not trusted by your system, you can add it to the trust store of your Java installation or the certificate store of your operating system. This will allow your system to trust the certificate and establish a secure SSL connection. 3. Check network configuration: Ensure that there are no network or firewall issues preventing the SSL connection between your client and the Nifi server. Confirm that the correct ports (usually 8080 or 8443) are open and accessible. 4. Verify Nifi configuration: Double-check the Nifi configuration files, especially the nifi.properties file, to ensure that the SSL configuration is correctly set up. Pay attention to properties related to keystore, truststore, and SSL/TLS protocols. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. ... View more

1. On the Abari server host, locate the `alert-templates.xml` file. By default, it is located in the `/etc/ambari-server/conf` directory. 2. Open the `alert-templates.xml` file and search for the `` section. 3. Within the `` section, locate the `` tag and modify its content. 4. Save the changes to the `alert-templates.xml` file. 5. Restart Ambari server for the changes to take effec ... View more

This warning indicates that there might be an issue with the PKIX validation, which is related to the SSL certificates. PKIX validation is used to verify the trustworthiness of SSL certificates during the SSL handshake process. If the validation fails, it means that the SSL certificate cannot be trusted, potentially leading to connection issues. To resolve this issue, you can try the following steps: 1. Check the SSL certificate configuration: Verify that the SSL certificates are correctly configured in the Nifi cluster. Ensure that the certificates are valid and trusted. 2. Check the keystore and truststore: Ensure that the Keystore and Truststore files are properly configured and contain the necessary certificates. Make sure that they have not expired or been revoked. 3. Verify the server's hostname: Ensure that the server hostname in the SSL certificate matches the actual hostname of the Nifi cluster. If they do not match, it can cause PKIX validation failures. 4. Check the time synchronization: Ensure that the system time on all the machines in the Nifi cluster is synchronized. A time difference between machines can lead to certificate validation issues. 5. Update the Java truststore: If the SSL certificate is self-signed or issued by an intermediate CA, it might not be recognized by Java by default. You may need to import the certificate into the Java truststore using the keytool utility. 6. Restart Nifi and validate the cluster status: After making any changes or adjustments, restart Nifi and monitor the cluster status. Check if the disconnectivity issue is resolved.  ... View more

You can integrate Airflow with a monitoring tool such as Prometheus or Grafana. These tools provide advanced monitoring and alerting capabilities. You can configure thresholds and receive alerts when the job runtime exceeds the specified limit.   Alternatively, you can use a dedicated job monitoring tool like Apache Oozie or Azkaban, which also offer alerting mechanisms to monitor long-running jobs. These tools provide more comprehensive job management features and can be integrated with Airflow. ... View more

@josr89 Can you please provide the exact error you are getting?  Please check if you have the right set of permission on that file as well as the parent directory.    Also there could be possibility you are facing the trust store related issue so the complete stack of the error will help me to identify the issue.  ... View more