Skip to main content
Tulasi
Tulasi
Silver ⭐️⭐️⭐️
January 24, 2019
Solved

Unable to start YARN - NodeManager on role NodeManager

 

Execute command Start this NodeManager on role NodeManager 

Failed to start role

Supervisor returned FATAL. Please check the role log file, stderr, or stdout.

 

Environment details:

 

Version: Cloudera Express 5.15.0
Java VM Name: Java HotSpot(TM) 64-Bit Server VM
Java VM Vendor: Oracle Corporation
Java Version: 1.7.0_67
 
System details:
Linux optim-rhel72-uppu.development.unicomglobal.software 3.10.0-327.28.3.el7.x86_64 #1 SMP Fri Aug 12 13:21:05 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux

 

I have followed the steps under "Configuring TLS/SSL for HDFS, YARN and MapReduce" using the link https://www.cloudera.com/documentation/enterprise/5-15-x/topics/sg_hive_encryption.html
 
Service did not start successfully; not all of the required roles started: only 0/1 roles started. Reasons : Service has only 0 NodeManager roles running instead of minimum required 1

I see below error in the role log:

 

Error starting NodeManager
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Failed to initialize container executor
 at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:269)
 at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
 at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:562)
 at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:609)
Caused by: java.io.IOException: Linux container executor not configured properly (error=24)
 at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.init(LinuxContainerExecutor.java:199)
 at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:267)
 ... 3 more
Caused by: ExitCodeException exitCode=24: Invalid conf file provided : /etc/hadoop/conf.cloudera.yarn/container-executor.cfg
 at org.apache.hadoop.util.Shell.runCommand(Shell.java:604)
 at org.apache.hadoop.util.Shell.run(Shell.java:507)
 at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:789)
 at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.init(LinuxContainerExecutor.java:193)
 ... 4 more
 
SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down NodeManager at optim-rhel72-uppu.development.unicomglobal.software/10.1.72.3
************************************************************/
 
Any help highly appreciated.
 
Thanks,
Tulasi
 

 

 

 

lwang
lwangAnswer
Platinum ⭐️
February 11, 2019

Hi @Tulasi,

 

Sorry for my late reply. From the output you sent below:

 

[root@optim-rhel72-uppu ~]# id yarn
uid=1007(yarn) gid=1010(hadoop) groups=1010(hadoop)

 

This looks a little different than my test cluster. Can you please do this?

usermod -g yarn yarn
usermod -a -G hadoop yarn

 

Also, please paste the content of this file:

/opt/cloudera/parcels/CDH/meta/permissions.json

 

Thanks,

Li 

Li Wang, Technical Solution Manager
View in thread

17 replies

Jerry
Gold ⭐️
Jerry
Gold ⭐️
January 28, 2019
Hi Tulasi,

Could you please verify the "container-executor.group" are same on both from Cloudera manager (Yarn->Configuration->Container Executor Group) and /etc/hadoop/conf.cloudera.yarn/container-executor.cfg (from Node manager host)

Let us know if you have questions

Thanks
Jerry

Translate
Tulasi
TulasiAuthor
Silver ⭐️⭐️⭐️
January 29, 2019

Hi Jerry,

 

Here is what I have on my system:

 

/etc/hadoop/conf.cloudera.yarn

-r-------- 1 root hadoop  156 Jan 24 01:00 container-executor.cfg
-rw-r--r-- 1 root root   3894 Jan 17 22:56 core-site.xml
-rw-r--r-- 1 root root    617 Jan 17 22:56 hadoop-env.sh
-rw-r--r-- 1 root root   2729 Jan 17 22:56 hdfs-site.xml

 

Even if I change above file permission, after start, it changes back to the same permission.

 

From manager I have this

Container Executor Group = yarn

 

Upgrade also not allowing as it requires all services should be up and running.

 

Let me know if you need any more details.

 

Thanks,

Tulasi

 

Translate
Jerry
Gold ⭐️
Jerry
Gold ⭐️
January 29, 2019

Hi Tulasi,

 

Could you check the value of this property Container Executor Group from the file "container-executor.cfg" file and cross check with CM configuration

 

Thanks

Jerry

Translate
manuroman
manuroman
Gold ⭐️
January 29, 2019

Hi @Tulasi,

 

Try to kill running process on port used by Yarn Services and then Try to restart.

 

Regards,

Manu.

Translate
Tulasi
TulasiAuthor
Silver ⭐️⭐️⭐️
January 29, 2019
Hi Manu, I tried your suggestion and it didn't work. Thanks, Tulasi
Translate
Terms & ConditionsAccessibility statement