FAQ
Hi Dalia,

Appears that your Namenode did not start.
Can you describe the process you are attempting to start the cluster? Can
you also share the contents of the /var/log/hadoop-hdfs/*namenode*.log ?

Thanks,
Adam

On Tue, Nov 27, 2012 at 6:11 PM, Dalia Hassan wrote:

Dear all,

I am using CM 4.1, it was working properly. But as suggested if I will
close the host, I have to stop all the services. So I did so.

Do anyone has a solution to this problem ?

I am now trying to start the services, I got this error :

Service did not start successfully; not all of the required roles started: Service hdfs1 does not have sufficient running NameNodes.


Do anyone has a solution to this problem ?


--
Adam Smieszny
Cloudera | Systems Engineer | http://tiny.cloudera.com/about
917.830.4156 | http://www.linkedin.com/in/adamsmieszny

Search Discussions

  • Dalia Hassan at Nov 27, 2012 at 11:18 pm
    Dear all,

    I am using CM 4.1, it was working properly. But as suggested if I will
    close the host, I have to stop all the services. So I did so.

    Do anyone has a solution to this problem ?

    I am now trying to start the services, I got this error :

    Service did not start successfully; not all of the required roles
    started: Service hdfs1 does not have sufficient running NameNodes.


    Do anyone has a solution to this problem ?
  • Dalia Hassan at Nov 27, 2012 at 11:13 pm
    While checking the namenode, I found this exception:

    Command aborted because of exception: Command timed-out after 150 seconds



    On Wed, Nov 28, 2012 at 1:11 AM, Dalia Hassan wrote:

    Dear all,

    I am using CM 4.1, it was working properly. But as suggested if I will
    close the host, I have to stop all the services. So I did so.

    Do anyone has a solution to this problem ?

    I am now trying to start the services, I got this error :

    Service did not start successfully; not all of the required roles started: Service hdfs1 does not have sufficient running NameNodes.


    Do anyone has a solution to this problem ?

  • Adam Smieszny at Nov 27, 2012 at 11:18 pm
    Hi Dalia,

    Sorry, I was mistaken - though it appears that you found the right file -
    should be the contents of *.log.out

    You've sent me the contents, which make me think of a few issues:
    1) these logs are from November 21 - has anything happened since then??
    2) What is your /etc/hosts file please

    p.s. please include scm-users@ on your replies in case other folks have
    insight

    Thanks,
    Adam

    On Tue, Nov 27, 2012 at 6:12 PM, Dalia Hassan wrote:

    While checking the namenode, I found this exception:

    Command aborted because of exception: Command timed-out after 150 seconds



    On Wed, Nov 28, 2012 at 1:11 AM, Dalia Hassan wrote:

    Dear all,

    I am using CM 4.1, it was working properly. But as suggested if I will
    close the host, I have to stop all the services. So I did so.

    Do anyone has a solution to this problem ?

    I am now trying to start the services, I got this error :

    Service did not start successfully; not all of the required roles started: Service hdfs1 does not have sufficient running NameNodes.


    Do anyone has a solution to this problem ?


    --
    Adam Smieszny
    Cloudera | Systems Engineer | http://tiny.cloudera.com/about
    917.830.4156 | http://www.linkedin.com/in/adamsmieszny
  • Dalia Hassan at Nov 27, 2012 at 11:52 pm
    /etc/hosts:

    cat /etc/hosts
    127.0.0.1 localhost
    192.168.2.3 master1.medcloud.com
    # The following lines are desirable for IPv6 capable hosts
    ::1 ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters

    nothing happened it worked normally, so its weird that I didn't see my
    trials for today in log files.

    I checked all the log files concerning hdfs
    /var/log/hadoop-hdfs/hadoop-cmf-hdfs1-*-master1.medcloud.com.log.out
    Their last record was 25-11 and everything was working normally.
    I feel there is a problem in connection, although ssh is working properly
    On Wed, Nov 28, 2012 at 1:18 AM, Adam Smieszny wrote:

    Hi Dalia,

    Sorry, I was mistaken - though it appears that you found the right file -
    should be the contents of *.log.out

    You've sent me the contents, which make me think of a few issues:
    1) these logs are from November 21 - has anything happened since then??
    2) What is your /etc/hosts file please

    p.s. please include scm-users@ on your replies in case other folks have
    insight

    Thanks,
    Adam

    On Tue, Nov 27, 2012 at 6:12 PM, Dalia Hassan wrote:

    While checking the namenode, I found this exception:

    Command aborted because of exception: Command timed-out after 150 seconds



    On Wed, Nov 28, 2012 at 1:11 AM, Dalia Hassan wrote:

    Dear all,

    I am using CM 4.1, it was working properly. But as suggested if I will
    close the host, I have to stop all the services. So I did so.

    Do anyone has a solution to this problem ?

    I am now trying to start the services, I got this error :

    Service did not start successfully; not all of the required roles started: Service hdfs1 does not have sufficient running NameNodes.


    Do anyone has a solution to this problem ?


    --
    Adam Smieszny
    Cloudera | Systems Engineer | http://tiny.cloudera.com/about
    917.830.4156 | http://www.linkedin.com/in/adamsmieszny
  • Philip Zeyliger at Nov 27, 2012 at 11:24 pm

    On Tue, Nov 27, 2012 at 3:12 PM, Dalia Hassan wrote:

    While checking the namenode, I found this exception:

    Command aborted because of exception: Command timed-out after 150 seconds
    This typically means that the agent isn't heartbeating. If you go to the
    'hosts' tab, do you see the hosts heartbeating in?

    -- Philip
  • Philip Zeyliger at Nov 27, 2012 at 11:27 pm
    That means that the agent process isn't running on the host, or is
    otherwise failing. Try "sudo service cloudera-scm-agent start" and look in
    the logs in /var/log/cloudera-scm-agent/*.

    -- Philip
    On Tue, Nov 27, 2012 at 3:26 PM, Dalia Hassan wrote:

    Yes they are not heartbeating, what does that mean Philip?

    On Wed, Nov 28, 2012 at 1:24 AM, Philip Zeyliger wrote:


    On Tue, Nov 27, 2012 at 3:12 PM, Dalia Hassan wrote:

    While checking the namenode, I found this exception:

    Command aborted because of exception: Command timed-out after 150 seconds
    This typically means that the agent isn't heartbeating. If you go to the
    'hosts' tab, do you see the hosts heartbeating in?

    -- Philip

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedNov 27, '12 at 11:12p
activeNov 27, '12 at 11:52p
posts7
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase