Support Questions
Find answers, ask questions, and share your expertise

Trying to run an oozie job receiving a null pointer exception


I set up my workflow put it into hdfs as well and I try to run the conf directory the properties file with this syntax.

I am really not sure why it is not working if I have a typo in my workflow.xml or or if I need to modify some config setting. Thanks


Error message 


Here is the link to the error message, 




Rising Star

Pease show your file and your oozie submit command please.


A few base questions:

  1. Are you defining your properly in your
  2. Do you have a correct reference to your namenode that perhaps you are referencing in your workflow


You might also try looking at the Oozie logs, which may give you more details on the error.

Properties file 

# Environment settings
queueName      = default
kerberos_realm = A
jobTracker     = B:8032
nameNode       = hdfs://nameservice1
hive2_server   = C
hive2_port     = 10000
impala_server  = D:21000
edge_server    = E
jobTracker     = yarnrm
# Project specific paths
projectPath                  = /user/${}/oozie/mediaroom-logs
keyTabLocation               = /user/${}/keytabs

# job path = ${projectPath}/BXDB/wf

# Project specific jars and other libraries
oozie.libpath                = ${projectPath}/lib,${projectPath}/util

# Standard useful properties
oozie.use.system.libpath     = true     = true

# Keytab specifics
keyTabName                   = A.keytab
keyTabUsername               = A
focusNodeLoginIng            = A
focusNodeLogin               = A

# Email notification list
emailList = B
xml file 

<workflow-app xmlns="uri:oozie:workflow:0.4" name="bxdb">


		<credential name="hive2_credentials" type="hive2">

	<start to="sshFileTransfer"/>

	<action name="sshFileTransfer">
		<ssh xmlns="uri:oozie:ssh-action:0.1">
			<!-- Change the name of the script -->
			<args> B</args>
			<args> C</args>
			<capture-output />
		<ok to="process-bxdb"/>
		<error to="sendEmailDQ_SRC"/>

	<!-- Move from landing zone on HDFS to processing -->

	<!-- Emit whether data is complete or partial, together with timestamp -->

	<!-- Spark job to process the snapshots and cdr data -->
	<action name="process-bxdb">
		<spark xmlns="uri:oozie:spark-action:0.2">
			<name>Process BXDB</name>
			<spark-opts>--num-executors 8  --executor-cores 2 --executor-memory 4G --driver-memory 4g --driver-cores 2</spark-opts>
		<ok to="impala-refresh-iis"/>
		<error to="sendEmailDQ_SRC"/>

	<!-- Impala invalidate/refresh metadata -->
	<action name="impala-refresh-iis">
		<shell xmlns="uri:oozie:shell-action:0.3">
			<argument>refresh belltv_expl.bxdb_sproc_cataloguereport</argument>
		<ok to="end"/>
		<error to="fail"/>


	<action name="sendEmailDQ_SRC">
		<email xmlns="uri:oozie:email-action:0.1">
			<subject>Error in the workflow please verify</subject>
			<body>BXDB project returned an error please verify</body>
		<ok to="fail"/>
		<error to="fail"/>

	<kill name="fail">
		 <message>"BXDB  ingestion failure"</message>

	<end name='end'/>

command to run  


oozie job -run

Rising Star

Try addig some arguments into your Oozie run command like so:

$ oozie job -oozie http://localhost:11000/oozie -config -run


If those changes don't work for you might try the following:

  1. Put your out in HDFS in the same directory as your workflow, then use Hue FileBrowser to execute the workflow and see if that works.  To do that, just checkmark the workflow.xml and a button will appear for you to take action like a submit.
  2. Reduce your workflow down to a simple email, then test... add the SSH, then test... keep adding and testing along the way.  If things fail at the first and most simple test (email action), then we've eliminated the other actions as being the culprit, and likely quite a few of your variables too.