Skip to main content

Oozie says jar does not exist

After submitting an oozie shell action job, oozie logs say shell-launcher.jar does not exist.

JA008: File /var/tmp/oozie/oozie-oozi450698329702305.dir/shell-launcher.jar does not exist.

On the oozie server shell-luncher.jar exists in the local folder.

# locate shell-launcher.jar

In order to resolve this error, just crate hdfs folders and give appropriate permissions to them.

# su -l hdfs -c "hadoop fs -mkdir /var"
# su -l hdfs -c "hadoop fs -mkdir /var/tmp"
# su -l hdfs -c "hadoop fs -mkdir /var/tmp/oozie"
# su -l hdfs -c "hadoop fs -chmod -R 755 /var"
# su -l hdfs -c "hadoop fs -chown oozie:hdfs /var/tmp/oozie"


  1. In case of me, /var/tmp/oozie should exist on local file system, not on HDFS.
    After creating the directory, restart the Oozie server. Then there comes a lot of files under /var/tmp/oozie including *-launcher.jar files.

    '/var/tmp/oozie' is the value of variable of Oozie server start-up command line. You can check the value using 'ps -ef | grep oozie' where the Oozie server is running.


Post a Comment

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are,, respectively. Proper communication with other servers on the network we should use routing tables. There are three

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover. I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves. Master Node: (Centos 7.2) Slave1 Node: (Centos 7.2) Slave2 Node: (Centos 7.2) Edit System settings on each node: /etc/sysctl.conf Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub Apply grub config and reboot each node: Master Node: /etc/redis/6379.conf Slave1 Node: /etc/redis/6379.conf Slave2 Node: /etc/redis/6379.conf Master Node: /etc/redis/sentinel.conf Slave1 Node: /etc/redis/sentinel.conf Slave2 Node: /etc/redis/sentinel.conf Each Node: /etc/systemd/system/ Each Node: /etc/