Member since
09-13-2022
23
Posts
0
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3381 | 12-26-2022 07:55 PM | |
1354 | 12-12-2022 10:10 PM | |
4126 | 11-10-2022 06:29 PM |
06-18-2024
01:25 AM
1 Kudo
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
11-21-2023
05:38 AM
The error indicates that the Hive Server Interactive (HSI) component is failing to start because the LLAP (Live Long and Process) app associated with it couldn't be started. To troubleshoot and resolve this issue, you can follow these general steps: Check LLAP Log Files: Look into the LLAP log files for more detailed error messages. These log files are typically located in a directory like /var/log/hive or a custom location configured in your environment. Examine the LLAP logs to identify any specific errors or issues that are preventing LLAP from starting. Verify LLAP Configuration: Check the LLAP configuration settings, including memory configurations, queue configurations, and other LLAP-specific parameters. Ensure that the configuration is correct and appropriate for your cluster resources. Verify that there are no typos or errors in the LLAP configuration files . Check Resource Availability: Ensure that there are sufficient resources (memory, CPU, etc.) available on the nodes where LLAP is supposed to run. Verify that LLAP is not competing for resources with other applications or services on the cluster. Check Hive Server Interactive Configuration: Review the configuration settings for Hive Server Interactive. Verify that the LLAP configuration is correctly specified in the Hive Server Interactive configurations. Ensure that the LLAP application name, number of instances, and other LLAP-related settings are accurate. Examine System Logs: Check the system logs on the nodes where LLAP is supposed to run. Look for any system-level issues or errors that might be affecting LLAP startup. Restart LLAP Manually: If LLAP fails to start during Hive Server Interactive startup, consider manually starting LLAP to see if you can get more detailed error messages. You can use commands like hive --service llap --start or the Ambari UI to start LLAP separately. Check for LLAP Process: After trying to start LLAP manually, check if the LLAP process is running. You can use tools like ps or jps to see if the LLAP daemon process is running on the expected nodes. Review Ambari Alerts: Check the Ambari Alerts for any warnings or errors related to Hive Server Interactive or LLAP. Ambari often provides helpful alerts and diagnostics. If the LLAP process is still not starting, the detailed logs and error messages should provide more insights into the root cause of the issue. Addressing the specific error or misconfiguration mentioned in the logs will be crucial in resolving the problem
... View more
10-24-2023
09:56 PM
Hi @myzard I think you need to verify the following things are set properly: 1. SPARK_HOME path 2. Python Environment paths
... View more
01-08-2023
06:44 AM
hello i am having same issue too any solution?
... View more
01-03-2023
08:58 AM
@myzard Can you please upload full error message which is above Traceback?
... View more
12-26-2022
07:55 PM
i solved it by re configure spark.jars & spark.submit.Pyfiles in spark interpreters
... View more
12-22-2022
11:59 PM
where can i get that jar ?
... View more
12-20-2022
07:02 PM
nothing just url to ranger in master 1
... View more
12-18-2022
07:15 PM
@myzard Increase the timeout below. You can also check after changing the below property from Ambari UI > Advance Hive-interactive-env:
Number of retries while checking LLAP app status = 40
(It will show a warning, please ignore that and save)
This should increase the timeout from 400 to 800s. 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
12-12-2022
10:10 PM
this setting in spark interpreter zeppelin
... View more