Re: Problem with Ambari 1.7 recognizing hosts running CentOS 6

2014-12-17 Thread David Novogrodsky
I am following the startup procedure listed here: https://cwiki.apache.org/confluence/display/AMBARI/Install+Ambari+1.7.0+from+Public+Repositories. I am trying to install HDP 2.1. Please note that these install instructions mention nothing about iptables or selinux. I am using CentOS 6 machines.

Re: Problem with Ambari 1.7 recognizing hosts running CentOS 6

2014-12-17 Thread David Novogrodsky
The error from the registration log is as follows: == Running setup agent script... == Agent log at: /var/log/ambari-agent/ambari- agent.log (WARNING 2014-12-17 10:43:08,349 NetUtil.py:92 - Server at https://namenode .

Re: Problem with Ambari 1.7 recognizing hosts running CentOS 6

2014-12-17 Thread David Novogrodsky
I am having problems adding mor ​​ information to this post: Delivery to the following recipient failed permanently: user@ambari.apache.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the server for the recipient domain

Re: Problem with Ambari 1.7 recognizing hosts running CentOS 6

2014-12-17 Thread Jeff Sposetti
Hi David, Try sending in plain/text, not HTML. On Wed, Dec 17, 2014 at 7:10 PM, David Novogrodsky david.novogrod...@gmail.com wrote: I am having problems adding mor ​​ information to this post: Delivery to the following recipient failed permanently: user@ambari.apache.org Technical

Re: Problem with Ambari 1.7 recognizing hosts running CentOS 6

2014-12-17 Thread David Novogrodsky
Please forgive me if I am sending this twice: I am having a problem with Ambari not recognizing nodes on a network. The cluster is using CentOS 6. I am trying to install HDP 2.1. I have the following values in my hosts file: 127.0.0.1 localhost localhost.localdomain localhost4

Re: Problem with Ambari 1.7 recognizing hosts running CentOS 6

2014-12-15 Thread Devopam Mittra
May I suggest you simply do a ssh -l keylessusername using the previous and the new FQDNs that you have defined to verify which one is in effect, and accessible ? Also, since you changed the FQDN, you may wish to simply reboot the cluster once, just to make sure that new ones are in-place. It