incubator-ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Sposetti <j...@hortonworks.com>
Subject Re: unable to register servers
Date Tue, 23 Apr 2013 22:17:05 GMT
Hi Artem,

This doesn't solve your immediate issue but FYI: there is a JIRA for the
ability to disable Ambari from distributing the .repo files during
installation.

https://issues.apache.org/jira/browse/AMBARI-2006

You can watch that JIRA for progress.

Thanks.


On Tue, Apr 23, 2013 at 3:02 PM, Siddharth Wagle <swagle@hortonworks.com>wrote:

> Please look at the section in repoinfo.xml that corresponds to your OS
> version. It should have both the HDP-1.2.1 and the HDP-epel repo sections.
>
> -Sid
>
> On Tue, Apr 23, 2013 at 2:38 PM, Artem Ervits <are9004@nyp.org> wrote:
>
>>  Ok I fixed this issue but the rest still remains. I have to manually
>> delete /etc/yum.repos.d/HDP.repo every time I run the installer because
>> Ambari deploys a new HDP.repo and HDP-epel.repo files. If there was a way
>> to force it to stop doing so. Like I said before, I already changed the
>> stacks file.****
>>
>> ** **
>>
>> *From:* Siddharth Wagle [mailto:swagle@hortonworks.com]
>> *Sent:* Tuesday, April 23, 2013 4:40 PM
>>
>> *To:* ambari-user@incubator.apache.org
>> *Subject:* Re: unable to register servers****
>>
>> ** **
>>
>> Hi Artem,
>>
>>
>> Could you verify that "hostname -f" on your managed host returns same
>> hostname that you used for registering the host ?
>>
>> -Sid****
>>
>>  On Tue, Apr 23, 2013 at 1:34 PM, Artem Ervits <are9004@nyp.org> wrote:**
>> **
>>
>> I also see this:****
>>
>>  ****
>>
>> warning: Could not retrieve fact fqdn****
>>
>> warning: Host is missing hostname and/or domain: test04****
>>
>> notice: Finished catalog run in 0.03 seconds****
>>
>> warning: Could not retrieve fact fqdn****
>>
>> warning: Host is missing hostname and/or domain: test04****
>>
>> notice: Finished catalog run in 0.03 seconds****
>>
>> warning: Could not retrieve fact fqdn****
>>
>> warning: Host is missing hostname and/or domain: test04****
>>
>>  ****
>>
>> I checked in /etc/hosts I have both test04 and test04.domain****
>>
>> I also added /etc/hostname file for Red Hat 6.4, saw that somewhere and
>> test04.domain is also there. /etc/sysconfig/network has test04 without
>> domain, can it be it?****
>>
>>  ****
>>
>> Thanks.****
>>
>>  ****
>>
>>  ****
>>
>> *From:* Artem Ervits [mailto:are9004@nyp.org]
>> *Sent:* Tuesday, April 23, 2013 4:28 PM****
>>
>>
>> *To:* ambari-user@incubator.apache.org
>> *Subject:* RE: unable to register servers****
>>
>>  ****
>>
>> I’m passed that error, it was NTP however, I’m cannot get past this
>> following issue:****
>>
>>  ****
>>
>> err:
>> /Stage[1]/Hdp::Snappy::Package/Hdp::Package[snappy]/Hdp::Package::Process_pkg[snappy]/Package[snappy-devel]/ensure:
>> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
>> -y install snappy-devel' returned 1: Error: Cannot retrieve repository
>> metadata (repomd.xml) for repository: HDP-1.2.1. Please verify its path and
>> try aga****
>>
>>  ****
>>
>> I am installing Ambari using local mirror. I ended up setting up a local
>> repo of HDP-1.2.1 as well, but I still seem to get the error. ****
>>
>>  ****
>>
>> *From:* Artem Ervits [mailto:are9004@nyp.org]
>> *Sent:* Tuesday, April 23, 2013 11:55 AM
>> *To:* ambari-user@incubator.apache.org
>> *Subject:* RE: unable to register servers****
>>
>>  ****
>>
>> I googled this error and article pointed to NTP. I checked clocks on all
>> servers and they’re indeed off. Will update the thread whether that was the
>> culprit.****
>>
>>  ****
>>
>> Thanks.****
>>
>>  ****
>>
>> *From:* Artem Ervits [mailto:are9004@nyp.org]
>> *Sent:* Monday, April 22, 2013 5:57 PM
>> *To:* ambari-user@incubator.apache.org
>> *Subject:* unable to register servers****
>>
>>  ****
>>
>> Hello all,****
>>
>>  ****
>>
>> I’m getting the following message when trying to do an initial install of
>> 1.2.2. Please advise how to work around this issue.****
>>
>>  ****
>>
>> ('INFO 2013-04-22 11:32:52,545 security.py:49 - SSL Connect being
>> called.. connecting to the server****
>>
>> INFO 2013-04-22 11:32:52,696 Controller.py:103 - Unable to connect to:
>> https://servername1:8441/agent/v1/register/servername5****
>>
>> Traceback (most recent call last):****
>>
>>   File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py",
>> line 88, in registerWithServer****
>>
>>     response = self.sendRequest(self.registerUrl, data)****
>>
>>   File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py",
>> line 237, in sendRequest****
>>
>>     self.cachedconnect = security.CachedHTTPSConnection(self.config)****
>>
>>   File "/usr/lib/python2.6/site-packages/ambari_agent/security.py", line
>> 77, in __init__****
>>
>>     self.connect()****
>>
>>   File "/usr/lib/python2.6/site-packages/ambari_agent/security.py", line
>> 82, in connect****
>>
>>     self.httpsconn.connect()****
>>
>>   File "/usr/lib/python2.6/site-packages/ambari_agent/security.py", line
>> 66, in connect****
>>
>>     ca_certs=server_crt)****
>>
>>   File "/usr/lib64/python2.6/ssl.py", line 338, in wrap_socket****
>>
>>     suppress_ragged_eofs=suppress_ragged_eofs)****
>>
>>  File "/usr/lib64/python2.6/ssl.py", line 120, in __init__****
>>
>>     self.do_handshake()****
>>
>>   File "/usr/lib64/python2.6/ssl.py", line 279, in do_handshake****
>>
>>     self._sslobj.do_handshake()****
>>
>> SSLError: [Errno 1] _ssl.c:490: error:14090086:SSL
>> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed****
>>
>> ', None)****
>>
>>  ****
>>
>>  ****
>>
>> Artem Ervits****
>>
>> Artem@nyp.org****
>>
>> New York Presbyterian Hospital****
>>
>>  ****
>>
>>
>> This electronic message is intended to be for the use only of the named
>> recipient, and may contain information that is confidential or privileged.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution or use of the contents of this message is
>> strictly prohibited. If you have received this message in error or are not
>> the named recipient, please notify us immediately by contacting the sender
>> at the electronic mail address noted above, and delete and destroy all
>> copies of this message. Thank you.****
>>  ------------------------------
>>
>>
>> Confidential Information subject to NYP's (and its affiliates')
>> information management and security policies (
>> http://infonet.nyp.org/QA/HospitalManual).****
>>
>>
>> This electronic message is intended to be for the use only of the named
>> recipient, and may contain information that is confidential or privileged.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution or use of the contents of this message is
>> strictly prohibited. If you have received this message in error or are not
>> the named recipient, please notify us immediately by contacting the sender
>> at the electronic mail address noted above, and delete and destroy all
>> copies of this message. Thank you.****
>>  ------------------------------
>>
>>
>> Confidential Information subject to NYP's (and its affiliates')
>> information management and security policies (
>> http://infonet.nyp.org/QA/HospitalManual).****
>>
>>
>> This electronic message is intended to be for the use only of the named
>> recipient, and may contain information that is confidential or privileged.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution or use of the contents of this message is
>> strictly prohibited. If you have received this message in error or are not
>> the named recipient, please notify us immediately by contacting the sender
>> at the electronic mail address noted above, and delete and destroy all
>> copies of this message. Thank you.****
>>  ------------------------------
>>
>>
>> Confidential Information subject to NYP's (and its affiliates')
>> information management and security policies (
>> http://infonet.nyp.org/QA/HospitalManual).****
>>
>>
>> This electronic message is intended to be for the use only of the named
>> recipient, and may contain information that is confidential or privileged.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution or use of the contents of this message is
>> strictly prohibited. If you have received this message in error or are not
>> the named recipient, please notify us immediately by contacting the sender
>> at the electronic mail address noted above, and delete and destroy all
>> copies of this message. Thank you.****
>>
>> ** **
>>
>> This electronic message is intended to be for the use only of the named
>> recipient, and may contain information that is confidential or privileged.
>> If you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution or use of the contents of this message is
>> strictly prohibited. If you have received this message in error or are not
>> the named recipient, please notify us immediately by contacting the sender
>> at the electronic mail address noted above, and delete and destroy all
>> copies of this message. Thank you.
>>
>
>

Mime
View raw message