You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2014/08/08 00:41:12 UTC
[jira] [Updated] (OOZIE-1920) Capture Output for SSH Action doesn't
work
[ https://issues.apache.org/jira/browse/OOZIE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Kanter updated OOZIE-1920:
---------------------------------
Fix Version/s: 4.1.0
> Capture Output for SSH Action doesn't work
> ------------------------------------------
>
> Key: OOZIE-1920
> URL: https://issues.apache.org/jira/browse/OOZIE-1920
> Project: Oozie
> Issue Type: Bug
> Components: action
> Affects Versions: 4.0.0
> Environment: CDH 5.0.2
> Reporter: Alessandro Costantino
> Priority: Blocker
> Labels: cloudera, oozie, ssh
> Fix For: 4.1.0
>
> Attachments: OOZIE-1920.patch
>
>
> Running a simple workflow that have a shell action with capture-output enabled, the SShActionExecutor look at the wrong stdout file. This is the the command that I found in the log:
> ssh -o PasswordAuthentication=no -o KbdInteractiveDevices=no -o StrictHostKeyChecking=no -o ConnectTimeout=20 workflow@redhat5 cat oozie-oozi/0000008-140708170302737-oozie-oozi-W/fileProcessing--ssh/22350.0000008-140708170302737-oozie-oozi-W@fileProcessing@1.stdout
> But the generated stdout file is `/home/instadoc/oozie-oozi/0000008-140708170302737-oozie-oozi-W/fileProcessing--ssh/22350.0000008-140708170302737-oozie-oozi-W@fileProcessing@0.stdout`
> If you relaunch the action the ID that prepend the .stdout extension could vary (ie: @9.stdout, @4.stdout) but the SShActionExecutor looks always at @0.stdout.
--
This message was sent by Atlassian JIRA
(v6.2#6252)