You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2006/06/06 22:14:29 UTC

[jira] Created: (HADOOP-279) running without the hadoop script causes warnings about log4j not being configured correctly

running without the hadoop script causes warnings about log4j not being configured correctly
--------------------------------------------------------------------------------------------

         Key: HADOOP-279
         URL: http://issues.apache.org/jira/browse/HADOOP-279
     Project: Hadoop
        Type: Improvement

  Components: mapred  
    Versions: 0.3.1    
    Reporter: Owen O'Malley
 Assigned to: Owen O'Malley 
     Fix For: 0.3.1


Anyone who runs hadoop programs without the bin/hadoop script will get a message about log4j not being configured correctly. The problem is that the config file uses the system property "hadoop.root.logger", which is set in the script.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (HADOOP-279) running without the hadoop script causes warnings about log4j not being configured correctly

Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-279?page=all ]

Owen O'Malley updated HADOOP-279:
---------------------------------

    Attachment: default-hadoop-root-logger.patch

This patch sets default values for the three system properties that are used in the default property files.

hadoop.root.logger=INFO,stdout
hadoop.log.dir=.
hadoop.log.file=hadoop.log

It also includes some examples of increasing logging levels.

> running without the hadoop script causes warnings about log4j not being configured correctly
> --------------------------------------------------------------------------------------------
>
>          Key: HADOOP-279
>          URL: http://issues.apache.org/jira/browse/HADOOP-279
>      Project: Hadoop
>         Type: Improvement

>   Components: mapred
>     Versions: 0.3.1
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>      Fix For: 0.3.1
>  Attachments: default-hadoop-root-logger.patch
>
> Anyone who runs hadoop programs without the bin/hadoop script will get a message about log4j not being configured correctly. The problem is that the config file uses the system property "hadoop.root.logger", which is set in the script.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (HADOOP-279) running without the hadoop script causes warnings about log4j not being configured correctly

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-279?page=all ]
     
Doug Cutting resolved HADOOP-279:
---------------------------------

    Fix Version: 0.3.2
                     (was: 0.3.1)
     Resolution: Fixed

I just committed this.  Thanks, Owen.

> running without the hadoop script causes warnings about log4j not being configured correctly
> --------------------------------------------------------------------------------------------
>
>          Key: HADOOP-279
>          URL: http://issues.apache.org/jira/browse/HADOOP-279
>      Project: Hadoop
>         Type: Improvement

>   Components: mapred
>     Versions: 0.3.1
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>      Fix For: 0.3.2
>  Attachments: default-hadoop-root-logger.patch
>
> Anyone who runs hadoop programs without the bin/hadoop script will get a message about log4j not being configured correctly. The problem is that the config file uses the system property "hadoop.root.logger", which is set in the script.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira