Re: Ambari Unable to start Hive server 2 after enabling security

Hi Alex/Rob, Thank you for giving the patch for this issue. After applying the patch, Ambari able to start "hiveserver2" without any manual kinit. Regards, Shaik On 6 May 2015 at 07:22, Alexander Denissov wrote: > To have Ambari 1.7.0 work with HDP 2.2.4 and secure Hive you will most > likely

Re: Ambari Unable to start Hive server 2 after enabling security

To have Ambari 1.7.0 work with HDP 2.2.4 and secure Hive you will most likely need to apply a patch (from Ambari 2.0) : https://issues.apache.org/jira/browse/AMBARI-9535 -- Thanks, Alex. On Tue, May 5, 2015 at 5:24 AM, Robert Levas wrote: > Hi Shaik… > > That is a good question. According to

Re: Ambari 2.0 agent failure to install due to permission denied

I was able to fix the problem by following advice here: http://hortonworks.com/community/forums/topic/ambari-server-upgrade-error-1-6-1-7-doc/ On Tue, May 5, 2015 at 3:26 PM, Artem Ervits wrote: > perhaps this can shed more light: > > ERROR: ambari-agent start failed. For more details, see > /v

Re: Ambari 2.0 agent failure to install due to permission denied

perhaps this can shed more light: ERROR: ambari-agent start failed. For more details, see /var/log/ambari-agent/ambari-agent.out: import hostname File "/usr/lib/python2.6/site-packages/ambari_agent/hostname.py", line 24, in import AmbariConfig File "/usr/lib/pytho

Re: Restarting nodes to avoid HTTP 403

If restarting the agents fixes everything, can you explain when you first encounter the warnings? Is this only after a cluster deployment? You can also check to see if this is some sort of web client issue by issuing the following GET: http://server/api/v1/clusters//alerts?fields=*&Alert/state.

RE: Restarting nodes to avoid HTTP 403

Indeed, I did not gave so much information about my problem, sorry about that. Here is your answers : 1) Version of Ambari --> I'm using Ambari 2.0 2) Whether the environment is kerberized --> Not it's not. Kerberos security is not enabled on this cluster. 3) Are you running the Ambari agent as

Re: Restarting nodes to avoid HTTP 403

Can you provide some more information on your environment, such as: 1) Version of Ambari 2) Whether the environment is kerberized 3) Are you running the Ambari agent as root, or another user. 4) Any information from the ambari-agent.log file that might seen to indicate a problem 5) You said that

Restarting nodes to avoid HTTP 403

Hi, I have currently some issues with cluster nodes. According to the Ambari web User Interface, I have 11 alerts linked to the fact that all nodes (except the monitoring one) return HTTP 403 response for services such as NameNode web UI, DataNode web UI, or NodeManager Health. The first weird

Re: Ambari 2.0 - Blueprint with configuration fails

Indeed it was an upgrade from Ambari 1.6.0. We did an install from scratch and it worked well. Thanks Jonathan ! 2015-04-30 18:28 GMT+02:00 Jonathan Hurley : > Is this an upgrade from Ambari 1.7.0? If so, you might be hitting > https://issues.apache.org/jira/browse/AMBARI-10665 > > Seems like

Re: Ambari Unable to start Hive server 2 after enabling security

Hi Shaik… That is a good question. According to https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2, it doesn’t appear that a kinit is needed before starting up the server. Rob From: Shaik M mailto:munna.had...@gmail.com>> Reply-To: "user@ambari.apache.org

Re: Ambari Unable to start Hive server 2 after enabling security

Ambari Team, can you please check, why it is required to do manual "kinit" for HiveServer2 startup? On 4 May 2015 at 22:24, Shaik M wrote: > Hi, > > After verifying the Amabri agent log, I logged in as "hive" user and I > ran below command. > > /usr/bin/kinit -kt /etc/security/keytabs/hdfs.h