[ 
https://issues.apache.org/jira/browse/OOZIE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rusty Martin updated OOZIE-2114:
--------------------------------
    Attachment: Failing Oozie Launcher.png

> Email Notification Limited when there is a failure
> --------------------------------------------------
>
>                 Key: OOZIE-2114
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2114
>             Project: Oozie
>          Issue Type: Improvement
>          Components: monitoring, tools
>    Affects Versions: 4.0.1
>         Environment: CentOS, CDH 5.3
>            Reporter: Rusty Martin
>              Labels: features
>             Fix For: trunk
>
>         Attachments: Failing Oozie Launcher.png
>
>
> When a job action fails the email notification is limited to the failing 
> oozie launcher which is less than helpful when determining the issue. See 
> screen shot. 
> Is there a way or can the function be added to include any error line, or an 
> option added to include the stderr log as an attachment? 
> For example if the action fails, the email would include anything in the body 
> of the email that has ERROR in the line of the log. 
> 3057 [main] ERROR org.apache.sqoop.SqoopOptions  - It seems that you have 
> launched a Sqoop metastore job via
>   3057 [main] ERROR org.apache.sqoop.SqoopOptions  - Oozie with 
> sqoop.metastore.client.record.password disabled.
>   3057 [main] ERROR org.apache.sqoop.SqoopOptions  - But this configuration 
> is not supported because Sqoop can't
>   3057 [main] ERROR org.apache.sqoop.SqoopOptions  - prompt the user to enter 
> the password while being executed
>   3057 [main] ERROR org.apache.sqoop.SqoopOptions  - as Oozie tasks. Please 
> enable sqoop.metastore.client.record
>   3057 [main] ERROR org.apache.sqoop.SqoopOptions  - .password in 
> sqoop-site.xml, or provide the password
>   3057 [main] ERROR org.apache.sqoop.SqoopOptions  - explicitly using 
> --password in the command tag of the Oozie



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to