Created on 01-24-2016 07:11 PM - edited 09-16-2022 02:59 AM
Hi,
After upgrading to CDH 5.5.1 from CDH 5.4.2 we started getting many errors in our oozie workflows which used to work smoothly.
One of the errors are related to email action which started throwing nullpointerexception.
I am not finding much INFO to share as logs only seen is NullPointerException:null as error.
Pasting below our oozie email action:
<action name="killEmail">
<email xmlns="uri:oozie:email-action:0.1">
<to>${emailRecipients}</to>
<subject>Oozie Workflow Run Error On abc-hist Workflow</subject>
<body>Oozie workflow id: ${wf:id()}, run failed.Error Message: [ ${wf:errorMessage(wf:lastErrorNode())} ]
</body>
</email>
<ok to="kill"/>
<error to="kill"/>
</action>
Can you please help us out !!!!
Thanks
Created 02-05-2016 12:11 PM
We're aware of this issue and there's a fix coming in CDH 5.5.2.
In the meantime, you can add the following to your oozie-site.xml (or safety-valve in CM's Oozie configuration) as a workaround:
<property> <name>oozie.email.smtp.password</name> <value>aaa</value> </property>
The value can be any string (it won't actually be used if oozie.email.smtp.auth is false, the default).
For those interested, this is fixed by OOZIE-2365.
Created 01-26-2016 08:38 AM
i know this issue cause i have got this error too. i think this is a bug.
there are two kind errors like below;
1) you have fill username and passwd, the errors is like your password is wrong,(in fact it's right passwd)
2) you didn't fill username and passwd, you will got NULLpoint error.
how to slove this problem ?
change mail server. you can test oozie mail service through third-part mail server ,eg: google
Created 01-31-2016 10:20 AM
We do have this issue too. (After Update)
I have not set Username/Password since we do not need authentification on our smtp server.
I get a Null Pointer Exception, which seems to be a bug. Has anybody a workaround ?
(Even if i set username/password i get the same error)
thanks...
Created 02-05-2016 12:11 PM
We're aware of this issue and there's a fix coming in CDH 5.5.2.
In the meantime, you can add the following to your oozie-site.xml (or safety-valve in CM's Oozie configuration) as a workaround:
<property> <name>oozie.email.smtp.password</name> <value>aaa</value> </property>
The value can be any string (it won't actually be used if oozie.email.smtp.auth is false, the default).
For those interested, this is fixed by OOZIE-2365.
Created 02-08-2016 05:07 PM
Hi,
can we enable the oozie.email.smtp.auth from cloudera manager UI ?