Hi ,
My weekly job looks for 7 prior days daily job done flag.I wanted this
weekly job to timeout if input criteria is not met.So I am using
<controls>
<timeout>10</timeout>
<concurrency>4</concurrency>
</controls>
What¹s the best way to send an email notification for a timeout.
Thanks
Sathi
On 9/14/14, 10:02 PM, "Shwetha GS" <[email protected]> wrote:
>Sorry, I have no idea about the error
>
>On Fri, Sep 12, 2014 at 5:07 PM, Raja.Aravapalli
><[email protected]
>> wrote:
>
>> Thanks a lot Swetha.
>>
>> I was able to locate the log for SSH. Thank you very much.
>>
>> Can you help me fix the below issue I am facing with Java action... ?
>>
>>
>>
>>
>>-------------------------------------------------------------------------
>>---------------------------
>> Oozie Java Action (oozie version 4.0.0-cdh5.1.0) - Exception from
>> container-launch
>>
>>
>>-------------------------------------------------------------------------
>>---------------------------
>>
>> I am trying to execute mapreduce application thru oozie java action on
>> YARN, when i try to execute the application, its failing in java action
>> with below error message:
>>
>> Exception from container-launch:
>> org.apache.hadoop.util.Shell$ExitCodeException:
>> org.apache.hadoop.util.Shell$ExitCodeException:
>> at org.apache.hadoop.util.Shell.runCommand(Shell.java:511)
>> at org.apache.hadoop.util.Shell.run(Shell.java:424)
>> at
>>
>>org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:656)
>> at
>>
>>org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launch
>>Container(DefaultContainerExecutor.java:195)
>> at
>>
>>org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.Conta
>>inerLaunch.call(ContainerLaunch.java:300)
>> at
>>
>>org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.Conta
>>inerLaunch.call(ContainerLaunch.java:81)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> at
>>
>>java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java
>>:1145)
>> at
>>
>>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav
>>a:615)
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>> Container exited with a non-zero exit code 1
>>
>> FYI
>> 1. We have recently upgraded our CDH cluster to CDH 5.1 from CDH 4.7
>> 2. We have recently upgraded Oozie from 3.X to 4.0.0
>> 3. The same application worked absolutely fine in oozie befor upgrade
>> to oozie 4.0.0 and CDH upgrade
>> 4. The MR application is working absolutely fine when run on command
>> line with below command but failing only when run thru oozie java action
>>
>>
>> hadoop jar <<-MyJar->> <<-JobDriver->> <<-inputDir->> <<-outputDir->>
>>
>>
>>
>> Regards,
>> Raja.
>>
>>
>>
>> -----Original Message-----
>> From: Shwetha GS [mailto:[email protected]]
>> Sent: Friday, September 12, 2014 2:54 PM
>> To: [email protected]
>> Subject: Re: where will log for SSH action is available in oozie ?
>>
>> It should be in <home directory>/oozie-oozi/<workflow id> on target
>>machine
>>
>> On Fri, Sep 12, 2014 at 2:42 PM, Raja.Aravapalli <
>> [email protected]
>> > wrote:
>>
>> > Hi Swetha:
>> >
>> >
>> >
>> >
>> >
>> > Can I know with what name the the log of SSH action will be saved.
>> >
>> >
>> > I specified the ssh user to use as like, xyz@12345-6789.
>> >
>> >
>> >
>> >
>> >
>> > I verified in the server 12345-6789, logging in as user xyz, but I am
>> > not seeing any log there in respect to oozie ssh action. Possibly I am
>> > missing out something,... can you guide me little more...
>> >
>> >
>> >
>> >
>> >
>> > Regards,
>> >
>> > Raja.
>> >
>> >
>> >
>> >
>> > -----Original Message-----
>> > From: Shwetha GS [mailto:[email protected]]
>> > Sent: Friday, September 12, 2014 11:07 AM
>> > To: [email protected]
>> > Subject: Re: where will log for SSH action is available in oozie ?
>> >
>> >
>> >
>> > check in the home directory of the ssh user on the ssh target machine
>> >
>> >
>> >
>> > -Shwetha
>> >
>> >
>> >
>> > On Fri, Sep 12, 2014 at 12:01 AM, Raja.Aravapalli <
>> > [email protected]<mailto:[email protected]>> wrote:
>> >
>> >
>> >
>> > > Hi
>> >
>> > >
>> >
>> > > Yeah. I tried <capture-output/>.
>> >
>> > >
>> >
>> > > But the thing is ... SSH isn't triggering itself...
>> >
>> > >
>> >
>> > > Also, trying to debug only with <capture-ouput/> doesn't work always
>> >
>> > > except for a few usecases....
>> >
>> > >
>> >
>> > > Having a log shown of execution of every command gives better look
>> > > to
>> >
>> > > the execution, but seems like SSH action in oozie doesn't provide
>> >
>> > > that...!! [ or I am lacking knowledge on how to check this...]
>> >
>> > >
>> >
>> > >
>> >
>> > > Pls guide me... Thanks.
>> >
>> > >
>> >
>> > > Regards,
>> >
>> > > Raja.
>> >
>> > >
>> >
>> > > -----Original Message-----
>> >
>> > > From: Sathi Chowdhury [mailto:[email protected]]
>> >
>> > > Sent: Thursday, September 11, 2014 11:21 PM
>> >
>> > > To: [email protected]<mailto:[email protected]>
>> >
>> > > Subject: Re: where will log for SSH action is available in oozie ?
>> >
>> > >
>> >
>> > > Hi Raja,
>> >
>> > > Did you try <capture-output/> in your workflow?
>> >
>> > > Thanks
>> >
>> > > Sathi
>> >
>> > >
>> >
>> > > On 9/11/14, 10:47 AM, "Raja.Aravapalli" <[email protected]
>> > <mailto:[email protected]>>
>> >
>> > > wrote:
>> >
>> > >
>> >
>> > > >Hi
>> >
>> > > >
>> >
>> > > >Is there anyway we can get a log for SSH action in oozie. Hard to
>> >
>> > > >identify that, SSH actions log cannot be identified.
>> >
>> > > >
>> >
>> > > >My SSH action is not even triggering and failing, I couldn't find
>> > > >any
>> > log.
>> >
>> > > >
>> >
>> > > >
>> >
>> > > >
>> >
>> > > >Can some one pls help me where I can get the logs for SSH actions
>>??
>> >
>> > > >
>> >
>> > > >
>> >
>> > > >
>> >
>> > > >
>> >
>> > > >
>> >
>> > > >Regards,
>> >
>> > > >Raja.
>> >
>> > >
>> >
>> > >
>> >
>> >
>> >
>> > --
>> >
>> > _____________________________________________________________
>> >
>> > The information contained in this communication is intended solely for
>> > the use of the individual or entity to whom it is addressed and others
>> > authorized to receive it. It may contain confidential or legally
>> > privileged information. If you are not the intended recipient you are
>> > hereby notified that any disclosure, copying, distribution or taking
>> > any action in reliance on the contents of this information is strictly
>> > prohibited and may be unlawful. If you have received this
>> > communication in error, please notify us immediately by responding to
>> > this email and then delete it from your system. The firm is neither
>> > liable for the proper and complete transmission of the information
>> > contained in this communication nor for any delay in its receipt.
>> >
>>
>> --
>> _____________________________________________________________
>> The information contained in this communication is intended solely for
>>the
>> use of the individual or entity to whom it is addressed and others
>> authorized to receive it. It may contain confidential or legally
>>privileged
>> information. If you are not the intended recipient you are hereby
>>notified
>> that any disclosure, copying, distribution or taking any action in
>>reliance
>> on the contents of this information is strictly prohibited and may be
>> unlawful. If you have received this communication in error, please
>>notify
>> us immediately by responding to this email and then delete it from your
>> system. The firm is neither liable for the proper and complete
>>transmission
>> of the information contained in this communication nor for any delay in
>>its
>> receipt.
>>
>
>--
>_____________________________________________________________
>The information contained in this communication is intended solely for
>the
>use of the individual or entity to whom it is addressed and others
>authorized to receive it. It may contain confidential or legally
>privileged
>information. If you are not the intended recipient you are hereby
>notified
>that any disclosure, copying, distribution or taking any action in
>reliance
>on the contents of this information is strictly prohibited and may be
>unlawful. If you have received this communication in error, please notify
>us immediately by responding to this email and then delete it from your
>system. The firm is neither liable for the proper and complete
>transmission
>of the information contained in this communication nor for any delay in
>its
>receipt.
