Community Articles
Find and share helpful community-sourced technical articles
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Labels (1)
Super Guru

When Oozie launcher(map only mapreduce job) gets scheduled to run on RHEL7 node in a mixed OS environment, it may get failed with below ERROR(stderr section of Oozie launcher logs):

Container: container_e1XX_XXXXXXX_0X_00000X on XXXXXX_XXX_XXXXXX
LogAggregationType: AGGREGATED
Log Upload Time:Tue XXXXXXXXXXXX
Log Contents:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See for further details.
/usr/bin/env: bash: No such file or directory
Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.ShellMain], exit code [1]
log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.impl.MetricsSystemImpl).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See for more info.


Why it failed?

This happens because "/bin" and "/sbin" missing in your $PATH in container launch environment.

$PATH variable gets derived from nodemanager's env and nodemanager get's the env from ambari-agent's /var/lib/ambari-agent/


How to fix this?

To fix this, add "/bin" and "/sbin" in /var/lib/ambari-agent/, restart ambari-agent followed by nodemanager restart.


Note - It may get failed with "ln: command not found" error, please follow the same resolution mentioned above in this case as well.


Please comment if you have any feedback/questions/suggestions. Happy Hadooping!! :)

0 Kudos
Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
1 of 1
Last update:
‎10-19-2018 08:57 PM
Updated by:
Top Kudoed Authors