Hi,   Are you using --password-file option inside your workflow? I have found a bug[1][2] similar to the issue you are facing. If this is the issue can you turn off the uber mode and try the job?   <global> <configuration> <property> <name>oozie.launcher.mapreduce.job.ubertask.enable</name> <value>false</value> </property> </configuration> </global>   Also are you doing any FileSystem.close() call in your actions?  FileSystem objects are automatically cached in Hadoop and thereby if you close the FileSystem object inside from your Java Action Class, which runs in the same JVM as the launcher map task, the singular FileSystem instance itself gets closed. Hence, when the Wrapper/Launcher wishes to exit normally.   Regards, Chethan YM Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   [1]. https://issues.apache.org/jira/browse/SQOOP-2997 [2]. https://jira.cloudera.com/browse/CDH-43107       ... View more