org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor

Exception from container-launch with container ID: container_1466017117730_0007_02_000001 and exit code: 1 ExitCodeException exitCode=1:

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web19

  • via Google Groups by PaulON, 10 months ago
    Exception from container-launch with container ID: container_1466017117730_0007_02_000001 and exit code: 1 ExitCodeException exitCode=1:
  • via Google Groups by Lev, 1 year ago
    Exception from container-launch with container ID: container_1428135716222_0003_02_000001 and exit code: 1 ExitCodeException exitCode=1:
  • Exception from container-launch with container ID: container_1499666177243_0002_02_000001 and exit code: 1 ExitCodeException exitCode=1:
  • Stack trace

    • org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: Exception from container-launch with container ID: container_1466017117730_0007_02_000001 and exit code: 1 ExitCodeException exitCode=1: at org.apache.hadoop.util.Shell.runCommand(Shell.java:538) at org.apache.hadoop.util.Shell.run(Shell.java:455) at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:715) at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:211) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:302) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:82) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.