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

Gagan commented on YARN-4037:
-----------------------------

Hi Mohammed,

I reverted the property to 
  <property>
    <name>mapreduce.jobhistory.address </name>
    <value>Garima-PC:10020</value>
  </property>
  <property>
    <name>mapreduce.jobhistory.webapp.address</name>
    <value>Garima-PC:19888</value>
  </property>
in map reduce.xml
and to 
<property> 
   <name>yarn.log.server.url</name> 
   <value>http://Garima-PC:19888/jobhistory/logs</value>
   <description>URL for job history server  </description>
  </property>
in yarn-site.xml. Restarted everything!!
I am directed to 
http://garima-pc:19888/jobhistory/logs/Garima-PC:49552/container_1439399185544_0001_02_000001/container_1439399185544_0001_02_000001/Garima
 
again the link is broken. Could you tell me if I can check the logs anywhere 
else, I need to find what went wrong with running the wordcount.jar example ?


> Hadoop - failed redirect for container
> --------------------------------------
>
>                 Key: YARN-4037
>                 URL: https://issues.apache.org/jira/browse/YARN-4037
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 2.7.1
>         Environment: Windows 7, Apache Hadoop 2.7.1
>            Reporter: Gagan
>         Attachments: mapred-site.xml, yarn-site.xml
>
>
> I believe this issue has been addressed earlier in 
> https://issues.apache.org/jira/browse/YARN-1473 though I am not sure because 
> the description of the JIRA does not talk about the following message 
> Failed while trying to construct the redirect url to the log server. Log 
> Server url may not be configured
> java.lang.Exception: Unknown container. Container either has not started or 
> has already completed or doesn't belong to this node at all.
> Could some one look at the same and provide detail on the root cause and 
> resolution ?



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

Reply via email to