Support Questions
Find answers, ask questions, and share your expertise
Check out our newest addition to the community, the Cloudera Innovation Accelerator group hub.

ResourceManager does not start

New Contributor

I installed Hadoop (HDP 2.5.3) on 4 VMs with Ambari (1 Ambari Server and 3 Ambari Clients; with the DNS entries server, node0, node1, node2) with HDFS, YARN, MapReduce and Zookeeper.

However, YARN doesn't want to start. When starting the Resource Manager on node1 I get the following error:

<code>resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -sS -L -w '%{http_code}' -X GET 'http://node0:50070/webhdfs/v1/ats/done/?op=GETFILESTATUS&' 1>/tmp/tmpgsiRLj 2>/tmp/tmpMENUFa' returned 7. curl: (7) Failed to connect to node0 port 50070: connection refused 000

App Timeline Server and History Server on node1 don't want to start either. Zookeeper, NameNode, DataNode and Nodemanager on Node0 is up. The nodes can reach each other (tried with ping, tested via ip and via dns-names) so that shouldn't be the problem.

Hopefully one can help me. I'm really new to this topic and not really familiar with the system.


Super Mentor

@Alexander E

As you mentioned that the Zookeeper, NameNode, DataNode and Nodemanager on Node0 is up. The nodes can reach each other nodes.

- But is the NameNode healthy ? I means do you see any error in the NameNode log?

- Sometimes even though the NameNode is running but it is running outofmemory (or OS resource unavailability/ like too many open sockets ...etc) and hence not able to respond. So better to check the Name Node log.

New Contributor

Ambari says the namenode is running and healthy:


So i restarted the namenode and wartched the log. There is an "RetriableException: NameNode still not started"

2017-02-12 16:24:58,249 INFO  namenode.NameNode ( - STARTUP_MSG:
STARTUP_MSG: Starting NameNode
STARTUP_MSG:   user = hdfs
STARTUP_MSG:   host = node0/
STARTUP_MSG:   args = []
STARTUP_MSG:   version =
STARTUP_MSG:   classpath = ...
STARTUP_MSG:   build = -r 9828acfdec41a121f0121f556b09e2d112259e92; compiled by 'j
enkins' on 2016-11-29T18:37Z
STARTUP_MSG:   java = 1.8.0_77
2017-02-12 16:24:58,268 INFO  namenode.NameNode ( - registered UNIX signal handlers for [TERM,
2017-02-12 16:24:58,271 INFO  namenode.NameNode ( - createNameNode []
2017-02-12 16:24:58,709 INFO  impl.MetricsConfig ( - loaded properties from hadoop-met

2017-02-12 16:25:01,416 INFO  ipc.Server ( - IPC Server Responder: starting
2017-02-12 16:25:01,417 INFO  ipc.Server ( - IPC Server listener on 8020: starting
2017-02-12 16:25:01,429 INFO  namenode.NameNode ( - NameNode RPC up at: node0/127
2017-02-12 16:25:01,430 INFO  namenode.FSNamesystem ( - Starting services re
quired for active state
2017-02-12 16:25:01,436 INFO  blockmanagement.CacheReplicationMonitor ( - Starting
 CacheReplicationMonitor with interval 30000 milliseconds
2017-02-12 16:25:03,040 INFO  ipc.Server ( - IPC Server handler 0 on 8020, call org.apach
e.hadoop.hdfs.server.protocol.DatanodeProtocol.sendHeartbeat from Call#687 Retry#0
org.apache.hadoop.ipc.RetriableException: NameNode still not started
        at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.checkNNStartup(
        at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.sendHeartbeat(
        at org.apache.hadoop.hdfs.protocolPB.DatanodeProtocolServerSideTranslatorPB.sendHeartbeat(DatanodeProtocolServer
        at org.apache.hadoop.hdfs.protocol.proto.DatanodeProtocolProtos$DatanodeProtocolService$2.callBlockingMethod(Dat
        at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$
        at org.apache.hadoop.ipc.RPC$
        at org.apache.hadoop.ipc.Server$Handler$
        at org.apache.hadoop.ipc.Server$Handler$
        at Method)
        at org.apache.hadoop.ipc.Server$
2017-02-12 16:25:03,080 INFO  fs.TrashPolicyDefault (<init>(224)) - The configured checkpoint in
terval is 0 minutes. Using an interval of 360 minutes that is used for deletion instead

I cannot poste the complete log so you can find it here: complete log

@Alexander E

Please login to ambari UI and check if the namenode service is started or not.

Since from the logs below it seems your namenode is down -

 Failed to connect to node0 port 50070: connection refused

Also it might happen sometimes, the namenode takes long time to start and before that if the Yarn is started it tried to connect namenode (which is still getting up)

For such scenario's make sure namenode is up and then restart YARN service again.

New Contributor

Jay SenSharma also said it could be a problem with the namenode so I posted the namenode.log where it says: "RetriableException: NameNode still not started"