Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08D4810044 for ; Mon, 15 Dec 2014 19:40:52 +0000 (UTC) Received: (qmail 83645 invoked by uid 500); 15 Dec 2014 19:40:51 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 83613 invoked by uid 500); 15 Dec 2014 19:40:51 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 83562 invoked by uid 99); 15 Dec 2014 19:40:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 19:40:51 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of david.novogrodsky@gmail.com designates 209.85.216.42 as permitted sender) Received: from [209.85.216.42] (HELO mail-qa0-f42.google.com) (209.85.216.42) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 19:40:47 +0000 Received: by mail-qa0-f42.google.com with SMTP id n4so2239370qaq.29 for ; Mon, 15 Dec 2014 11:40:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=n4It0KWhaWqatAII/lBSdykqHiPSMtvurZj+yovZlvc=; b=t9WPme8pnhxhm+RLO8XBxPs8Qu9hvnS3NJ2x7CbjM9k5GhVjLUdwMsigNnUqi0Juez R8QKATe//RzQsSxkmGfa4wQKkfdEoKsD9fB5JwAtYI9pwmgybfw4V85NOG6Y8dzUJRxe fsKOlOfIAlbQRFTrgvif7IWdJqGorTBzPzd+PlUTLugN1llhaNBRudlsu/EY+c2/oZcw ChKnlw2Kd2uWQhdrAkyG98ruw5QU5dgJTMcNtTyubGCUKYtju24S7QRbtFYibX6zh2kY L0mDSMLQhb0DGzODUUJuKR2dIKYy77SpEEAd/fkjm50oTbY+rW/evJEUf9aAz1vJ16eq GDEg== X-Received: by 10.140.104.169 with SMTP id a38mr56045286qgf.35.1418672426554; Mon, 15 Dec 2014 11:40:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.134.16 with HTTP; Mon, 15 Dec 2014 11:40:06 -0800 (PST) From: David Novogrodsky Date: Mon, 15 Dec 2014 13:40:06 -0600 Message-ID: Subject: Ambari does not recognize the node Ambari is running on. To: "user@ambari.apache.org" Content-Type: multipart/alternative; boundary=001a11352eda099ac8050a466aac X-Virus-Checked: Checked by ClamAV on apache.org --001a11352eda099ac8050a466aac Content-Type: text/plain; charset=UTF-8 Ambari is running on the namenode of my Hadoop cluster. Can Ambari be put on the same node as the master/namenode of the cluster or does Ambari need to go on a seperate host? During the Confirm Hosts phase, Ambari does not recognize the hose it is running on. The plan is Ambari will be running on the same host as the namenode. Ambari is able to recognize the other nodes in the network. Here is the error message I get: Command start time 2014-12-15 13:32:23 {'exitstatus': 1, 'log': "Host registration aborted. Ambari Agent host cannot reach Ambari Server 'localhost.namenode:8080'. Please check the network connectivity between the Ambari Agent host and the Ambari Server"} Connection to localdomain.namenode closed. SSH command execution finished host=localdomain.namenode, exitcode=1 Command end time 2014-12-15 13:32:24 ERROR: Bootstrap of host localdomain.namenode fails because previous action finished with non-zero exit code (1) ERROR MESSAGE: tcgetattr: Invalid argument Connection to localdomain.namenode closed. STDOUT: {'exitstatus': 1, 'log': "Host registration aborted. Ambari Agent host cannot reach Ambari Server 'localhost.namenode:8080'. Please check the network connectivity between the Ambari Agent host and the Ambari Server"} Connection to localdomain.namenode closed. Here are the entries for the local hosts file: xxx.xxx.200.144 localhost.datanode10 xxx.xxx.200.107 localhost.datanode01 xxx.xxx.200.143 localdomain.namenode namenode David Novogrodsky david.novogrodsky@gmail.com http://www.linkedin.com/in/davidnovogrodsky --001a11352eda099ac8050a466aac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Amb= ari is running on the namenode of my Hadoop cluster.=C2=A0 Can Ambari be pu= t on the same node as the master/namenode of the cluster or does Ambari nee= d to go on a seperate host?

During the Confirm Hosts phase, Ambari d= oes not recognize the hose it is running on.=C2=A0 The plan is Ambari will = be running on the same host as the namenode.=C2=A0 Ambari is able to recogn= ize the other nodes in the network.

Here is the error message I get:
Command start time 2014-12-15 13:32:23
{'exitstatus': 1, 'log': "Host registration aborted. A=
mbari Agent host cannot reach Ambari Server 'localhost.namenode:8080=
9;. Please check the network connectivity between the Ambari Agent host and=
 the Ambari Server"}

Connection to localdomain.namenode closed.
SSH command execution finished
host=3Dlocaldomain.namenode, exitcode=3D1
Command end time 2014-12-15 13:32:24

ERROR: Bootstrap of host localdomain.namenode fails because previous action=
 finished with non-zero exit code (1)
ERROR MESSAGE: tcgetattr: Invalid argument
Connection to localdomain.namenode closed.

STDOUT: {'exitstatus': 1, 'log': "Host registration ab=
orted. Ambari Agent host cannot reach Ambari Server 'localhost.namenode=
:8080'. Please check the network connectivity between the Ambari Agent =
host and the Ambari Server"}

Connection to localdomain.namenode closed.
Here are the entries for th= e local hosts file:
xxx.xxx.200.144 localhost.datanode10
xxx.xxx.200.= 107 localhost.datanode01
xxx.xxx.200.143 localdomain.namenode namenode
--001a11352eda099ac8050a466aac--