Return-Path: <yarn-issues-return-88070-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 02A6E200B39
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Sat,  4 Jun 2016 02:37:01 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id F420E160A49; Sat,  4 Jun 2016 00:37:01 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 6BBB7160A55
	for <archive-asf-public@cust-asf.ponee.io>; Sat,  4 Jun 2016 02:37:00 +0200 (CEST)
Received: (qmail 95333 invoked by uid 500); 4 Jun 2016 00:36:59 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 95223 invoked by uid 99); 4 Jun 2016 00:36:59 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jun 2016 00:36:59 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 5503C2C1F6A
	for <yarn-issues@hadoop.apache.org>; Sat,  4 Jun 2016 00:36:59 +0000 (UTC)
Date: Sat, 4 Jun 2016 00:36:59 +0000 (UTC)
From: "Xuan Gong (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12969418.1463094514000.31235.1465000619344@Atlassian.JIRA>
In-Reply-To: <JIRA.12969418.1463094514000@Atlassian.JIRA>
References: <JIRA.12969418.1463094514000@Atlassian.JIRA> <JIRA.12969418.1463094514991@arcas>
Subject: [jira] [Commented] (YARN-5080) Cannot obtain logs using YARN CLI
 -am for either KILLED or RUNNING AM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Sat, 04 Jun 2016 00:37:01 -0000


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

Xuan Gong commented on YARN-5080:
---------------------------------

Did the manual test by add configuration "yarn.resourcemanager.bind-host" , and verified that with the new patch it worked fine.

> Cannot obtain logs using YARN CLI -am for either KILLED or RUNNING AM
> ---------------------------------------------------------------------
>
>                 Key: YARN-5080
>                 URL: https://issues.apache.org/jira/browse/YARN-5080
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 2.8.0
>            Reporter: Sumana Sathish
>            Assignee: Xuan Gong
>            Priority: Critical
>             Fix For: 2.8.0
>
>         Attachments: YARN-5080.1.patch, YARN-5080.2.patch, YARN-5080.3.patch
>
>
> When the application is running, if we try to obtain AM logs using 
> {code}
> yarn logs -applicationId <applicationId> -am 1
> {code}
> It throws the following error
> {code}
> Unable to get AM container informations for the application:<applicationId>
> Illegal character in scheme name at index 0: 0.0.0.0://<hostname>
> {code} 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org