falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-187) Update Falcon start script to also redirect stdout to the log file
Date Tue, 12 Nov 2013 02:16:18 GMT

    [ https://issues.apache.org/jira/browse/FALCON-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819740#comment-13819740
] 

Arpit Gupta commented on FALCON-187:
------------------------------------

btw this patch will apply on top of FALCON-162 and FALCON-165. I used hadoop scripts as a
guideline for this change as in the same env i could start hadoop scripts via ssh but not
falcon.

> Update Falcon start script to also redirect stdout to the log file 
> -------------------------------------------------------------------
>
>                 Key: FALCON-187
>                 URL: https://issues.apache.org/jira/browse/FALCON-187
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.3
>            Reporter: Arpit Gupta
>            Assignee: Arpit Gupta
>             Fix For: 0.4
>
>         Attachments: FALCON-187-v1.patch
>
>
> I noticed a weird behavior where if the bin/falcon-start script was called within the
ssh call it would start the service but not return the control back to the user.
> If the same ssh call was issued with -t option it worked. What i determined is that the
java command being issued is only redirecting stderr to the log file and stdout is not being
captured. If we capture stdout as well we do not run into this issue.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message