[ http://issues.apache.org/jira/browse/HADOOP-309?page=all ]
Owen O'Malley updated HADOOP-309:
---------------------------------
Fix Version: 0.4.0
Priority: Minor (was: Major)
As we discussed offline, this is just caused because you didn't define a value
for "hadoop.log.dir" on your java command line. It would be good to have the
server not crash when the property is not defined, but the property should be
defined for the servers. The two obvious "fixes" are to:
1. Remove the "/logs" context when no "hadoop.log.dir" property is defined.
This will be confusing to users.
2. See if we can get the value from log4j via the jakarta commons logging
api. It looks like there might be routines that will work.
In any case, I believe this is a pretty low priority bug.
> NullPointerException in StatusHttpServer
> ----------------------------------------
>
> Key: HADOOP-309
> URL: http://issues.apache.org/jira/browse/HADOOP-309
> Project: Hadoop
> Type: Bug
> Components: mapred, dfs
> Versions: 0.3.2
> Reporter: Konstantin Shvachko
> Priority: Minor
> Fix For: 0.4.0
>
> The NullPointerException happens in the constructor of StatusHttpServer
> because the System property "hadoop.log.dir" is undefined.
> I see it trying to start the Namenode directly without using any scripts.
> Exception in thread "main" java.lang.NullPointerException
> at org.mortbay.util.Resource.newResource(Resource.java:99)
> at
> org.mortbay.http.ResourceCache.setResourceBase(ResourceCache.java:140)
> at org.mortbay.http.HttpContext.setResourceBase(HttpContext.java:2207)
> at
> org.apache.hadoop.mapred.StatusHttpServer.<init>(StatusHttpServer.java:66)
> at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:172)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:97)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:88)
> at org.apache.hadoop.dfs.NameNode.main(NameNode.java:496)
> In general I think the sources should not rely on the system properties and
> environment variables defined in hadoop scripts.
--
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
