Member since
03-11-2020
197
Posts
30
Kudos Received
40
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1514 | 11-07-2024 08:47 AM | |
1147 | 11-07-2024 08:36 AM | |
840 | 06-18-2024 01:34 AM | |
560 | 06-18-2024 01:25 AM | |
743 | 06-18-2024 01:16 AM |
06-18-2024
01:16 AM
1 Kudo
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
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
07-31-2023
11:44 PM
@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
07-31-2023
11:33 PM
@h2rr821 Please perform the below steps. Identify compatible version Backup of the existing Cloudera PostgreSQL JDBC driver files Download the new PostgreSQL JDBC driver files. Stop Cloudera services using the PostgreSQL JDBC driver Replace old JAR files with the new ones Ensure new JAR files have correct permissions. Start services: Restart Cloudera services. 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
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-27-2023
09:40 PM
@kobolock If you are seeing the same below error then you can you can try the following solution. SSLError: Failed to connect. Please check openssl library versions. To resolve this issue, add the following property in ambari-agent.ini (/etc/ambari-agent/conf/ambari-agent.ini) file under [security]and restart ambari-agent:
========
[security]
force_https_protocol=PROTOCOL_TLSv1_2 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
04-27-2023
09:28 PM
@harry_12 Could please confirm the below things? >> If that user is a local user (Means its created through ambari UI )? If yes that user will not be able to login to your OS. >> Where does this user belong to Is it coming from AD or Ldap? >> Where you are trying to ssh? What server is that ? >> Are you doing curl on Ambari URL and trying to access with that user? If thats the case, then it should be able to curl. >> Please attach some screenshot of this event to understand it better.
... View more
04-17-2023
11:23 PM
Hello @itsmezeeshan, Hope you are doing good. Its not recommended to clear the space from this location. As these the binaries for the Cloudera Manager packages for the following services (cloudera-host-monitor, cloudera-scm-agent, cloudera-scm-eventserver, cloudera-scm-headlamp, cloudera-scm-server, cloudera-scm-server-db, cloudera-service-monitor) [root@mprl509 lib]# du -sh cloudera-* 1.3G cloudera-host-monitor 300K cloudera-scm-agent 20M cloudera-scm-eventserver 4.6M cloudera-scm-headlamp 3.0G cloudera-scm-server 272M cloudera-scm-server-db 5.5G cloudera-service-monitor I would like to recommend you to please increase the disk space to 20 GB More.
... View more