[
https://issues.apache.org/jira/browse/AMBARI-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle reopened AMBARI-5705:
-------------------------------------
AMBARI-5722
> 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)
