Member since
06-20-2016
308
Posts
103
Kudos Received
29
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1956 | 09-19-2018 06:31 PM | |
1442 | 09-13-2018 09:33 PM | |
1409 | 09-04-2018 05:29 PM | |
4415 | 08-27-2018 04:33 PM | |
3484 | 08-22-2018 07:46 PM |
08-23-2018
01:46 PM
hi, @Akhil S Naik is correct, my memory was on the limit, do you know why i can't change the configuration of the different services on ambari? i have to add an SmartSense ID to start it
... View more
08-22-2018
04:38 PM
Hi @yadir Aguilar ,
i think you should have started the ambari-server using the command
ambari-server start
In that case please use the command
ambari-server status
This is just how systemd works. For systemd to track a process it needs to be started with systemd.
If it is started outside systemd, it won't manage the process and the status will be "not started"
E.g:
# valid flow
ambari-server start
ambari-server status
# valid flow
systemctl start ambari-server
systemctl status ambari-server
# invalid flow
ambari-server start
systemctl status ambari-server
Please accept answer if this helps you :)
... View more
08-21-2018
03:37 PM
thanks @Akhil S Naik i believe that the error was resolved
... View more
05-28-2019
10:35 AM
Hi Amarnath, Will this work for Oozie? If not do you have similar log4j setting for oozie? Thanks, Sajin
... View more
08-15-2018
09:20 PM
Andy\Amarnath, My question was initially why my expected outcome was not working and why this other format did work. Along the way, I believe my question was answered, assuming my understanding is correct. I did't want to dive to deep as I thought it may be outside the scope of my initial post. Since the conversation has gone that way tho, Andy is correct. I did not understand the difference between 1-way SSL and 2-way SSL. Using 1-way SSL (keystore only) all HTTPS connections are accepted regardless if the source is who we are expecting or not. Using 2-way SSL only HTTPS connections are accepted but now we must verify who the source is by authenticating with a private key & server certificate that can be authenticated by my truststore. My use case for this knowledge, is we are promoting projects between our Dev & Prod clusters. I wanted to ensure we had the correct security in place to proceed. The developers are wanting 1-way SSL but I lacked the knowledge at the time to make it work and only had 2-way. They were upset because this required more data to be sent via REST protocol using 2-way. Now that I understand each protocol, I will not allow to them proceed to Production with their architecture without 2-way SSL. Originally, I was simply ignorant of how to setup 1-way SSL, without understanding the security hole it would make. Thank you both for your time and effort in reviewing this concept.
... View more
03-14-2019
12:30 PM
@amarnath reddy pappu, I followed these steps but when I login to ambari, it is successfully getting redirected to knox gateway and after i give credentials it goes to ambari ui and then coming back to knox gateway log in screen. Could you please suggest. Opened questions in community also: https://community.hortonworks.com/questions/242895/knox-sso-not-working-for-ambari.html
... View more
10-09-2018
01:24 PM
In the end, I created the new cluster with HDF 3.2.0. With NiFi Registry made it very fast. Thanks to all which tried to help.
... View more
08-07-2018
06:11 PM
2 Kudos
This is applicable for CentOS7/RHEL6 - for CentOS7/RHEL7 please follow https://community.hortonworks.com/articles/188269/javapython-updates-and-ambari-agent-tls-settings.html Upgrading to jdk1.8.0_171 version disables some of the TLSv1_1 TLSv1 protocols and algorithms. With this only option is using TLS1_2 version but CentOS6/RHEL6 uses Python 2.6 and it does not support TLS1_2. Agent-server communication would fail with below error. WARNING 2018-04-24 16:35:10,989 NetUtil.py:124 - Server at https://***.***.***.***:8440 is not reachable, sleeping for 10 seconds...INFO 2018-04-24 16:35:20,990 NetUtil.py:70 - Connecting to https://***.***.***.***:8440/caERROR 2018-04-24 16:35:20,991 NetUtil.py:96 - EOF occurred in violation of protocol (_ssl.c:579)ERROR 2018-04-24 16:35:20,991 NetUtil.py:97 - SSLError: Failed to connect. Please check openssl library versions.
To workaround this problem you can tweak /usr/jdk64/jdk1.8.0_112/jre/lib/security/java.security file in Ambari server host to enable some of the algorithms. From: jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC To: jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
EC keySize < 224, DES40_CBC, RC4_40 Please note that this is just a temporary workaround and it is recommended to Upgrade the OS version to use TLS1_2
... View more
Labels:
08-13-2018
01:02 PM
Hi @Saurabh, Please login and accept the answer if this helped you.
... View more
06-12-2017
03:24 PM
@amarnath reddy pappu @mqureshi, @Kuldeep Kulkarni, @Gerd Koenig, @Andrew Ryansmaple-mapreduce-job-error.txtmapreduce-error-in-hive-wiht-beeline.txt
We have enabled SSL/TLS on HDP cluster by following @amarnath reddy pappu blog :
https://community.hortonworks.com/articles/52875/enable-https-for-hdfs.html and HDP documentation.
Almost all service opening on Https defined port. But Only issue we are currently facing is : MAP
REDUCE JOBS ARE NOT LAUNCHING
We use hive through beeline connector. While executing query we receive error :
WARNING: Hive-on-MR is deprecated in Hive 2 and may not be available in the future versions. Consider using a different execution engine (i.e. spark, tez) or using Hive 1.X releases. Error: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask. java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty (state=08S01,code=1) Tried a Sample Map reduce Job alone as well. That also got failed. Error is long so attaching here.
I would appreciate your help. 🙂
... View more