Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E454017FB4 for ; Fri, 13 Mar 2015 20:01:47 +0000 (UTC) Received: (qmail 11003 invoked by uid 500); 13 Mar 2015 20:01:42 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 10903 invoked by uid 500); 13 Mar 2015 20:01:42 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 10893 invoked by uid 99); 13 Mar 2015 20:01:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2015 20:01:42 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gotomypc27@gmail.com designates 209.85.192.48 as permitted sender) Received: from [209.85.192.48] (HELO mail-qg0-f48.google.com) (209.85.192.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2015 20:01:17 +0000 Received: by qgdq107 with SMTP id q107so28619233qgd.7 for ; Fri, 13 Mar 2015 13:01:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=kZnRVETf2XR2MwyB3p18ChaQFcZk/bRhOxpOtsLbB1w=; b=Q9W66soTOELCRHPB/WQLamSrsF0dc4sjDBqBk/srvwgV7PZHWqPlvdfOH2/0o3e9YN wPtv2NDMdl/QEDykkHQtZ9AiBLfaIA95NHrdSgEC9i8xqqpozcg+hmueljWreehBi1kT UHkQKpZv8lL0DaeQ6zFsiXmObGubLEtrCtvijQ5+MPB8pNn4Ci940rQelaeHxs+A+6XG rzRLem5/gDy9DQxlMPGBNcRSlaHoHTOIVlgXUdjB/s33R2sqj611aesEQUAdMKx4WYrd 2tKEblMA1qTTNk1H/U4k+yLj5fGYe5adXbzDReZtQQMFjHS4oLJNDzqtKZQoDsUYd60L O/cg== MIME-Version: 1.0 X-Received: by 10.140.202.17 with SMTP id x17mr64323057qha.50.1426276875229; Fri, 13 Mar 2015 13:01:15 -0700 (PDT) Received: by 10.96.55.10 with HTTP; Fri, 13 Mar 2015 13:01:15 -0700 (PDT) In-Reply-To: <550321BD.4050609@aossama.com> References: <2125876D8382E34C9258B5B906E4EF5C1D1D2E98@chgpmaldag01wv.bcbsa.com> <550321BD.4050609@aossama.com> Date: Fri, 13 Mar 2015 13:01:15 -0700 Message-ID: Subject: Re: Cloudera Agent not starting From: Krish Donald To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a1141cd4c7fdf6f051130f6f0 X-Virus-Checked: Checked by ClamAV on apache.org --001a1141cd4c7fdf6f051130f6f0 Content-Type: text/plain; charset=UTF-8 I am using Elastic Ip Address and assigned Elastic Ip Address to the instances. After doing lot of trial and error , I could atleast install Cloudera Manager on AWS. But a very starnge thing I have notice, I am not sure if I am doing something wrong . When I have installed CM on AWS on an instance, it gave me message at the end to open the http://privateipaddress:7180 to open the cloudera manager GUI. However when I tried to open http://privateaddress:7180 it didn't open but when I tried opening http://Publicip:7180 How should I use only one type of ip address either public or private? On Fri, Mar 13, 2015 at 10:43 AM, Ahmed Ossama wrote: > You are getting this error either because the agent cannot bind to the > address assigned to the hostname nn1.amazonaws.com or the port 9000 is > already in use. > > Check that nn1.amazonaws.com points to an IP address that is actually > bound to the server. > > And check that no other processes are listening on port 9000 > > > On 03/13/2015 07:38 PM, Mauro Schneider wrote: > > Have you configured /etc/sysconfig/network ? I had the same issue without > to configure it. > > > > Atenciosamente, > > Mauro Schneider > > > 2015-03-12 14:39 GMT-03:00 Krish Donald : > >> Firewall is not running >> >> [root@ec2-52-10-19-232 ~]# netstat -anp | grep 9000 >> [root@ec2-52-10-19-232 ~]# service iptables status >> iptables: Firewall is not running. >> >> >> >> On Thu, Mar 12, 2015 at 7:36 AM, Gangavarupu, Venkata - Contingent Worker >> wrote: >> >>> Hey, >>> >>> >>> >>> Check if firewall is running that might create problem for the >>> installation. >>> >>> >>> >>> Thanks, >>> >>> Venkat >>> >>> >>> >>> *From:* Sean Busbey [mailto:busbey@cloudera.com] >>> *Sent:* Thursday, March 12, 2015 12:24 AM >>> *To:* user >>> *Subject:* Re: Cloudera Agent not starting >>> >>> >>> >>> Please send vendor specific questions to that vendor's support mechanism. >>> >>> >>> >>> Since your issue appears to be with Cloudera Manager, please use >>> http://community.cloudera.com/ >>> >>> >>> >>> >>> On Wed, Mar 11, 2015 at 11:54 PM, Krish Donald >>> wrote: >>> >>> Hi, >>> >>> >>> >>> I am trying to setup cluster but getting below error: >>> >>> >>> >>> error: No socket could be created on ('nn1.amazonaws.com >>> ', >>> 9000) -- [Errno 99] Cannot assign requested address >>> >>> >>> >>> I checked nothing is running on port 9000 . >>> >>> /etc/hosts file contains >>> >>> >>> >>> 127.0.0.1 localhost.amazonaws localhost >>> ::1 localhost.amazonaws localhost >>> 127.0.0.1 localhost.localdomain localhost >>> 127.0.0.1 localdomain localhost >>> 52.xx.xx.1 nn1.amazonaws.com >>> >>> nn1 >>> 52.xx.xx.2 nn2.amazonaws.com >>> >>> nn2 >>> 52.xx.xx.3 dn1.amazonaws.com >>> >>> dn1 >>> 52.xx.xx.4 dn2.amazonaws.com >>> >>> dn2 >>> 52.xx.xx.5 dn3.amazonaws.com >>> >>> dn3 >>> >>> >>> >>> >>> >>> The below script also giving the correct result i.e. correct hostname >>> and ip address. >>> >>> python -c 'import socket; print socket.getfqdn (), socket.gethostbyname >>> (socket.getfqdn ())' >>> >>> >>> >>> >>> >>> Not sure what else to look for. >>> >>> >>> >>> Please guide. >>> >>> >>> >>> Thanks >>> >>> >>> >>> Krish >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Sean >>> >> >> > > -- > Regards, > Ahmed Ossama > > --001a1141cd4c7fdf6f051130f6f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I am using Elastic Ip Address and assigned Elastic Ip= Address to the instances.

After doing lot of tria= l and error , I could atleast install Cloudera Manager on AWS.
But a very starnge thing I have notice, I am not sure if I am = doing something wrong .
When I have installed CM on AWS on an ins= tance, it gave me message at the end to open the http://privateipaddress:7180 to open = the cloudera manager GUI.

However when I tried to = open http://priva= teaddress:7180 it didn't open but when I tried opening http://Publicip:7180

How should I use only one type of =C2=A0ip address either p= ublic or private?

On Fri, Mar 13, 2015 at 10:43 AM, Ahmed Ossama <ahmed@aossama.= com> wrote:
=20 =20 =20
You are getting this error either because the agent cannot bind to the address assigned to the hostname nn1.amazonaws.com or the port 9000 is already in use.

Check that nn1.a= mazonaws.com points to an IP address that is actually bound to the server.

And check that no other processes are listening on port 9000


On 03/13/2015 07:38 PM, Mauro Schneider wrote:
Have you configured /etc/sysconfig/network ?=C2=A0 I= had the same issue without to configure it.



Atenciosamente,

Mauro Schneider


2015-03-12 14:39 GMT-03:00 Krish Donald <gotomypc27@gmail.com>:
Firewall is not running

[root@ec2-52-10-19-232 ~]# netstat -anp | grep 9000
[root@ec2-52-10-19-232 ~]# service iptables status
iptables: Firewall is not running.



On Thu, Mar 12, 2015 at 7:36 AM, Gangavarupu, Venkata - Contingent Worker <venkata.gangavarupu.cs@bcbsa.com> wrote:

Hey,

=C2=A0

Check if firewall is running that might create problem for the installation.

=C2=A0

Thanks,

Venkat

=C2=A0

From:<= /b> Sean Busbey [mailto:busbey@cloudera.com]
Sent: Thursday, March 12, 2015 12:24 AM
To: user
Subject: Re: Cloudera Agent not starting

=C2=A0

Please send vendor specific questions to that vendor's support mechanism.

=C2=A0

Since your issue appears to be with Cloudera Manager, please use=C2=A0http= ://community.cloudera.com/

=C2=A0

On Wed, Mar 11, 2015 at 11:54 PM, Krish Donald <gotomypc27@gmail.com<= /a>> wrote:

Hi,

=C2=A0

I am trying to setup cluster but getting below error:

=C2=A0

nn1.amazonaws.= com', 9000) -- [Errno 99] Cannot assign requested address=C2=A0

=C2=A0

I checked nothing is running on port 9000 .

/etc/hosts file contains

=C2=A0

127.0.0.1=C2= =A0=C2=A0 localhost.amazonaws localhost
::1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 localhost.amazonaws localhost
127.0.0.1=C2=A0=C2=A0 localhost.localdomain localhost
127.0.0.1=C2=A0=C2=A0 localdomain localhost
52.xx.xx.1 nn1.amazonaws.com nn1
52.xx.xx.2=C2=A0 nn2.amazonaws.com nn2
52.xx.xx.3 dn1.amazonaws.com dn1
52.xx.xx.4 dn2.amazonaws.com dn2
52.xx.xx.5=C2=A0 dn3.amazonaws.com dn3

=C2=A0

=C2=A0

The below script also giving the correct result i.e. correct hostname and ip address.

python -c 'import socket; print socket.getfqdn (), socket.gethostbyname (socket.getfqdn ())'

=C2=A0

=C2=A0

Not sure what else to look for.

=C2=A0

Please guide.<= /p>

=C2=A0

Thanks

=C2=A0

Krish

=C2=A0

=C2=A0

=C2=A0

=C2=A0



=C2=A0

--

Sean




--=20
Regards,
Ahmed Ossama

--001a1141cd4c7fdf6f051130f6f0--