Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Failed to start node manager role

Failed to start node manager role

New Contributor

Hello all - While starting services via Cloudera Manager, there is an error encountered at the step of starting YARN service. The error is related to starting node manager role on service YARN. Error details below. Appreciate your help on this.

 

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: Cannot run program "$FAKE_PATH/parcels/CDH-5.14.0-1.cdh5.14.0.p0.24/lib/hadoop-yarn/bin/container-executor": error=13, Permission denied at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at org.apache.hadoop.util.Shell.runCommand(Shell.java:551) 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:192) at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:267) ... 3 more Caused by: java.io.IOException: error=13, Permission denied at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 8 more

3 REPLIES 3

Re: Failed to start node manager role

Expert Contributor

Hi @whoami,

 

Cause: container-executor.cfg is configured with the below permissions, where yarn is the group name to which this file is associated. Thus, yarn user must be associated with yarn group so as to execute the container-executor program, else it will bail out due to permission issues.

 

In this case, yarn user was not associated with yarn group, but both were available.

 

Solution: Associate yarn user with the yarn group available in the system and try starting node manager again.

> usermod -G yarn yarn

 

 

Regards,

Manu.

Re: Failed to start node manager role

New Contributor

Hi @manuroman - Firstly, thanks for your response. 

 

user yarn seems to already associated with group yarn.

 

$ id yarn
uid=1124573(yarn) gid=810091(hadoop) groups=810091(hadoop),810072(yarn)

 

Still facing the problem while starting services via Cloudera manager. Request your help.

Highlighted

Re: Failed to start node manager role

Expert Contributor

Hi @whoami,

 

What are the permissions of this folder "$FAKE_PATH/parcels/CDH-5.14.0-1.cdh5.14.0.p0.24/lib/hadoop-yarn/bin/"  ?

 

Regards,

Manu.

Don't have an account?
Coming from Hortonworks? Activate your account here