Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 1 Jul 2013 23:43:20 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12652777.1371171461393.195327.1372722200197@arcas>
In-Reply-To: <JIRA.12652777.1371171461393@arcas>
References: <JIRA.12652777.1371171461393@arcas>
Subject: [jira] [Commented] (YARN-814) Difficult to diagnose a failed
 container launch when error due to invalid environment variable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jian He commented on YARN-814:
------------------------------

bq. Why is shExec.getOutput() being ignored ( and replaced with exception.getMessage() )? 
basically, shExec.getOutput is from stdout and exception.getMessage() is from stderr. shExec.getOutput is empty in the case that shExec throws an exception.
bq.Have you run this with a test script that emits information both to stdout and stderr?
If user manually redirects to stderr, the redirected message is missed, because the redirected err msg is only wrapped in ExitCodeException which is not thrown at all. 
                
> Difficult to diagnose a failed container launch when error due to invalid environment variable
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-814
>                 URL: https://issues.apache.org/jira/browse/YARN-814
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Hitesh Shah
>            Assignee: Jian He
>         Attachments: YARN-814.1.patch, YARN-814.2.patch, YARN-814.3.patch, YARN-814.patch
>
>
> The container's launch script sets up environment variables, symlinks etc. 
> If there is any failure when setting up the basic context ( before the actual user's process is launched ), nothing is captured by the NM. This makes it impossible to diagnose the reason for the failure. 
> To reproduce, set an env var where the value contains characters that throw syntax errors in bash. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira