[ https://issues.apache.org/jira/browse/HADOOP-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173043#comment-13173043 ]
Jingui Lee commented on HADOOP-7837: ------------------------------------ Thanks! I meet this problem before and this patch works well for my hadoop cluster. > no NullAppender in the log4j config > ----------------------------------- > > Key: HADOOP-7837 > URL: https://issues.apache.org/jira/browse/HADOOP-7837 > Project: Hadoop Common > Issue Type: Bug > Components: conf > Affects Versions: 0.23.0 > Environment: OS/X, no JAVA_HOME set > Reporter: Steve Loughran > Assignee: Eli Collins > Attachments: hadoop-7837-1.patch > > > running sbin/start-dfs.sh gives me a telling off about no null appender > -should one be in the log4j config file. > Full trace (failure expected, but full output not as expected) > {code} > ./start-dfs.sh > log4j:ERROR Could not find value for key log4j.appender.NullAppender > log4j:ERROR Could not instantiate appender named "NullAppender". > Incorrect configuration: namenode address dfs.namenode.servicerpc-address or > dfs.namenode.rpc-address is not configured. > Starting namenodes on [] > cat: > /Users/slo/Java/Hadoop/versions/hadoop-0.23.0/libexec/../etc/hadoop/slaves: > No such file or directory > cat: > /Users/slo/Java/Hadoop/versions/hadoop-0.23.0/libexec/../etc/hadoop/slaves: > No such file or directory > Secondary namenodes are not configured. Cannot start secondary namenodes. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira