nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (NUTCH-508) ${hadoop.log.dir} and ${hadoop.log.file} are not propagated to the tasktracker
Date Mon, 09 Jul 2007 13:48:04 GMT

    [ https://issues.apache.org/jira/browse/NUTCH-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511121
] 

Enis Soztutar commented on NUTCH-508:
-------------------------------------

Tasktracker invokes another jvm calling TaskTracker$Child but hadoop.log.dir is not passed
as a parameter. The logs of the user program is handled correctly but i suppose the this is
caused by the logs at TaskTracker$Child such as
LOG.debug("Child starting");
can not be logged. I suppose you can ask about this in hadoop-dev to see if it is indeed a
hadoop issue. 

> ${hadoop.log.dir} and ${hadoop.log.file} are not propagated to the tasktracker
> ------------------------------------------------------------------------------
>
>                 Key: NUTCH-508
>                 URL: https://issues.apache.org/jira/browse/NUTCH-508
>             Project: Nutch
>          Issue Type: Bug
>         Environment: Linux 2.6, Java1.6
>            Reporter: Emmanuel Joke
>             Fix For: 1.0.0
>
>
> As described in http://www.nabble.com/Crawl-error-with-hadoop-t3994217.html
> the log4j config file is missing some parameters.
> hadoop.log.dir=.
> hadoop.log.file=hadoop.log
> Thanks for the help of Mathijs

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message