[
https://issues.apache.org/jira/browse/AMBARI-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050527#comment-14050527
]
David Cameron commented on AMBARI-5705:
---------------------------------------
I would appreciate more details in the installation instructions about proxy
configuration. That was my issue.
I just rigged up a new Centos 6.5 VM with proxies configured from
/etc/profile.d. Then I verified that when I ssh into the rig it the proxy
settings are there. After installing and configuring ambari I then when
verified that Oracle JDK is configured in JAVA_HOME via /etc/profile.d. Then I
made sure it was configured to use the default browser proxy settings.
Somehow, still Ambari could not verify that the repositories are reachable. So
I went in and carefully configured Ambari proxy settings using
/var/lib/ambari-server/ambari-env.sh and that got ambari up and running. The
final proxy stumble was that somehow yum did not pick up proxies properly so I
configured it manually.
After that everything came up without a hitch.
> Fail to install hive client with error: Fail: Execution of '/bin/sh -c 'cd
> /usr/lib/ambari-agent/ && curl -kf --retry 5
> http://hadoop1:8080/resources/DBConnectionVerification.jar -o
> DBConnectionVerification.jar'' returned 22.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-5705
> URL: https://issues.apache.org/jira/browse/AMBARI-5705
> Project: Ambari
> Issue Type: Bug
> Components: controller, test
> Affects Versions: 1.5.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 1.6.0
>
> Attachments: AMBARI-5705.patch, AMBARI-5705_branch-1.6.0.patch
>
>
> PROBLEM: Fresh install of HDP 2.1, when deploying hive client it fail with
> error: Execution of '/bin/sh -c 'cd /usr/lib/ambari-agent/ && curl -kf
> --retry 5 http://hadoop1:8080/resources/DBConnectionVerification.jar -o
> DBConnectionVerification.jar'' returned 22.
> Steps to reproduce: set up a proxy (http_proxy="<proxy host that has not
> access to cluster>").
> Fix:
> Added
> {code}
> --noproxy <ambari-server hostname>
> {code}
> option to all our curl invocations that download files from ambari-server. I
> would go for this option because sometimes ftp_proxy may be used as well.
> Also, I've fixed an error message that is shown when jce_name property is not
> defined in a non-secure cluster and added a proper handling of this situation
> in secure cluster.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
