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.

enable kerberos,nodemanager can not start Exit code from container executor initialization is : 24

enable kerberos,nodemanager can not start Exit code from container executor initialization is : 24

New Contributor

************************************************************/
2014-09-16 17:30:56,298 INFO org.apache.hadoop.yarn.server.nodemanager.NodeManager: registered UNIX signal handlers for [TERM, HUP, INT]
2014-09-16 17:30:57,065 WARN org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor: Exit code from container executor initialization is : 24
org.apache.hadoop.util.Shell$ExitCodeException: Invalid conf file provided : /etc/hadoop/conf.cloudera.yarn/container-executor.cfg

at org.apache.hadoop.util.Shell.runCommand(Shell.java:511)
at org.apache.hadoop.util.Shell.run(Shell.java:424)
at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:656)
at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.init(LinuxContainerExecutor.java:169)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:142)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:351)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:398)
2014-09-16 17:30:57,079 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:
2014-09-16 17:30:57,079 INFO org.apache.hadoop.service.AbstractService: Service NodeManager failed in state INITED; cause: org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Failed to initialize container executor
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Failed to initialize container executor
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:144)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:351)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:398)
Caused by: java.io.IOException: Linux container executor not configured properly (error=24)
at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.init(LinuxContainerExecutor.java:175)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:142)
... 3 more
Caused by: org.apache.hadoop.util.Shell$ExitCodeException: Invalid conf file provided : /etc/hadoop/conf.cloudera.yarn/container-executor.cfg

at org.apache.hadoop.util.Shell.runCommand(Shell.java:511)
at org.apache.hadoop.util.Shell.run(Shell.java:424)
at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:656)
at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.init(LinuxContainerExecutor.java:169)
... 4 more
2014-09-16 17:30:57,085 FATAL org.apache.hadoop.yarn.server.nodemanager.NodeManager: 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:144)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:351)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:398)
Caused by: java.io.IOException: Linux container executor not configured properly (error=24)
at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.init(LinuxContainerExecutor.java:175)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:142)
... 3 more
Caused by: org.apache.hadoop.util.Shell$ExitCodeException: Invalid conf file provided : /etc/hadoop/conf.cloudera.yarn/container-executor.cfg

at org.apache.hadoop.util.Shell.runCommand(Shell.java:511)
at org.apache.hadoop.util.Shell.run(Shell.java:424)
at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:656)
at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.init(LinuxContainerExecutor.java:169)
... 4 more
2014-09-16 17:30:57,088 INFO org.apache.hadoop.yarn.server.nodemanager.NodeManager: SHUTDOWN_MSG:
/************************************************************

3 REPLIES 3

Re: enable kerberos,nodemanager can not start Exit code from container executor initialization is :

New Contributor

I am facing this same issue ... any update?

Re: enable kerberos,nodemanager can not start Exit code from container executor initialization is :

New Contributor

I am having the same issue. Has anyone found a resolution to this problem?

 

Re: enable kerberos,nodemanager can not start Exit code from container executor initialization is :

Super Collaborator

If you are not using Cloudera Manager you need to make sure that the configuration file is deployed to all nodes and in the proper place. CM handles this automatically for you (recent releases) but on older releases you might need to deploy the client config before starting the NM to make sure.

The original message was posted 2 years ago so most likely that was in an old release of Cloudera Manager and the solution would have been to deploy client config and restart the NM.

 

NOTE: The config file must be located relative to the binary container-executor. If it is not found then you will get a message like that. Manual deployments are not simple for this file.

 

Wilfred