Member since
03-11-2020
195
Posts
30
Kudos Received
40
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
944 | 11-07-2024 08:47 AM | |
708 | 11-07-2024 08:36 AM | |
625 | 06-18-2024 01:34 AM | |
357 | 06-18-2024 01:25 AM | |
623 | 06-18-2024 01:16 AM |
06-18-2024
01:10 AM
2 Kudos
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
06-18-2024
01:00 AM
1 Kudo
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
04-26-2024
07:12 AM
2 Kudos
if you want to force cdp onto rocky8: echo "ID_LIKE=\"Red Hat Enterprise Linux release 8.7 (Ootpa)\"" >> /etc/rocky-release this fixes install-agents hang echo "ID=\"rhel\"" >> /usr/lib/os-release this fixes install-parcels hang removing this ID var from os-release after deployment will cause hadoop to fail restart
... View more
08-01-2023
09:17 AM
1. Identify compatible version 2. Backup of the existing Cloudera PostgreSQL JDBC driver files(postgresql-42.3.2.jar,postgresql-42.3.3.jar, postgresql-42.2.16.jar) 3. Download the new PostgreSQL JDBC driver files(postgresql-42.6.0.jar, postgresql-42.2.27.jre7.jar, and postgresql-42.3.8.jar). 4. Stop Cloudera services using the Web-UI and command(I do not understand how to Stop Cloudera services using the PostgreSQL JDBC driver) 5. Replace old JAR files: /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.2.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.3.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.2.16.jar with the new ones /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.6.0.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.8.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.2.27.jre7.jar 6. Ensure new JAR files have correct permissions. 7. Start services: Restart Cloudera services. Then the schema registry server will has problem. It do run for a while, and it fail. I cannot successfully restart the schema registry server without put back the old jar file to the folder(/opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/)
... View more
08-01-2023
12:13 AM
1 Kudo
Hi @Kartik_Agarwal ! I solved this a couple of weeks ago, but you are right with your comments: In my case the file was having the right permission set, but the parent directory had not. So with the change of permissions to the parent directory, it worked fine. Thanks for your support!
... View more
07-12-2023
11:48 PM
@George-Megre There could be possibilities you are hitting the below issue. https://issues.apache.org/jira/browse/AMBARI-20068
... View more
05-31-2023
02:36 AM
@noekmc Change the keystore password: Use the following command to change the keystore password: keytool -storepasswd -keystore /path/to/keystore.jks
... View more
04-28-2023
05:04 AM
@harry_12 I believe that users which are created in Ambari are for logging into ambari UI. If you need an SSH user for a particular host, you should create that user in the node(s) operating system directly.
... View more
04-28-2023
01:26 AM
"none of the solutions from the internet are helping" 🙄. So I asked what binaries?
... View more
04-23-2023
11:10 PM
In addition as per your last comments, we can see you have a considerable amount of data under your /home directory. ex: 15G /home Could you please check if you can remove some data from it? Thanks
... View more