hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Krish Donald <gotomyp...@gmail.com>
Subject Re: Cloudera Agent not starting
Date Fri, 13 Mar 2015 20:01:15 GMT
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 <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 <ahmed@aossama.com> 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 <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,
>>>
>>>
>>>
>>> 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/
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__community.cloudera.com_&d=AwMFaQ&c=aIUDzRSH0GV4AQi9KEcOBQ&r=Q6FqyTxAatyPFtTsK6ghgTPkJfjL8rxaHWBrAFzranM&m=1jJIxa1X-SkcZeaCo0M-WlyX1peqQKxCuWyzgUJvP1Q&s=-2aTyiJDKALsZBR88RlkVyf4ILC5rIdwBPTSJxMo1Nk&e=>
>>>
>>>
>>>
>>> On Wed, Mar 11, 2015 at 11:54 PM, Krish Donald <gotomypc27@gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>
>>>
>>>
>>> I am trying to setup cluster but getting below error:
>>>
>>>
>>>
>>> error: No socket could be created on ('nn1.amazonaws.com
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__nn1.amazonaws.com&d=AwMFaQ&c=aIUDzRSH0GV4AQi9KEcOBQ&r=Q6FqyTxAatyPFtTsK6ghgTPkJfjL8rxaHWBrAFzranM&m=1jJIxa1X-SkcZeaCo0M-WlyX1peqQKxCuWyzgUJvP1Q&s=RgMnJmvsAG-GlOjUBNehkKy9NWffafzCEvDKvHTKPR0&e=>',
>>> 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
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__nn1.amazonaws.com&d=AwMFaQ&c=aIUDzRSH0GV4AQi9KEcOBQ&r=Q6FqyTxAatyPFtTsK6ghgTPkJfjL8rxaHWBrAFzranM&m=1jJIxa1X-SkcZeaCo0M-WlyX1peqQKxCuWyzgUJvP1Q&s=RgMnJmvsAG-GlOjUBNehkKy9NWffafzCEvDKvHTKPR0&e=>
>>> nn1
>>> 52.xx.xx.2  nn2.amazonaws.com
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__nn2.amazonaws.com&d=AwMFaQ&c=aIUDzRSH0GV4AQi9KEcOBQ&r=Q6FqyTxAatyPFtTsK6ghgTPkJfjL8rxaHWBrAFzranM&m=1jJIxa1X-SkcZeaCo0M-WlyX1peqQKxCuWyzgUJvP1Q&s=8qYOs45QR_WdPVObFq86xW6VhMczJqqYViTwdXHpqzQ&e=>
>>> nn2
>>> 52.xx.xx.3 dn1.amazonaws.com
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__dn1.amazonaws.com&d=AwMFaQ&c=aIUDzRSH0GV4AQi9KEcOBQ&r=Q6FqyTxAatyPFtTsK6ghgTPkJfjL8rxaHWBrAFzranM&m=1jJIxa1X-SkcZeaCo0M-WlyX1peqQKxCuWyzgUJvP1Q&s=DKqWRX0CZcNdcDyO_MEFeI_lxqK8l1z1ZS0UIn1F8GU&e=>
>>> dn1
>>> 52.xx.xx.4 dn2.amazonaws.com
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__dn2.amazonaws.com&d=AwMFaQ&c=aIUDzRSH0GV4AQi9KEcOBQ&r=Q6FqyTxAatyPFtTsK6ghgTPkJfjL8rxaHWBrAFzranM&m=1jJIxa1X-SkcZeaCo0M-WlyX1peqQKxCuWyzgUJvP1Q&s=_TMQimUQtr0D2B0sYQjodMu3JMwVfrraM2Pzv2VVt_U&e=>
>>> dn2
>>> 52.xx.xx.5  dn3.amazonaws.com
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__dn3.amazonaws.com&d=AwMFaQ&c=aIUDzRSH0GV4AQi9KEcOBQ&r=Q6FqyTxAatyPFtTsK6ghgTPkJfjL8rxaHWBrAFzranM&m=1jJIxa1X-SkcZeaCo0M-WlyX1peqQKxCuWyzgUJvP1Q&s=o_MjtGfG1w-s_GJ1jFg6w90L0elZbEgwZ6_bBq48_lk&e=>
>>> 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
>
>

Mime
View raw message