Hi anirbandd,

It's likely that you ran into OOZIE-2739. There is a workaround that requires to override the value for oozie.action.shell.setup.hadoop.conf.dir.log4j.content in oozie-site.xml.

If you are using Cloudera Manager, you can easiliy do it via using a Safety valve for Oozie.

Go to Cloudera Manager -> Oozie -> Configuration page and search for oozie-site.xml.

Add the following to "Oozie Server Advanced Configuration Snippet (Safety Valve) for oozie-site.xml" using the XML editor that is better for a newline value carrying config such as the following.

<property>
<name>oozie.action.shell.setup.hadoop.conf.dir.log4j.content</name>
<value>
log4j.rootLogger=INFO,console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.target=System.err
log4j.appender.console.layout=org.apache.log4j.PatternLayout
</value>
</property>

 Then click Save changes and Re-deploy client configuration (restart Oozie).