Hi all,

After a bit of thrashing with RSA keys and having to move /Nutch/src/webapps up to /Nutch, I've gotten the 1/12/2006 build of Nutch running on three servers.

The "master" is running as a NameNode & JobTracker, and two slaves are running as DataNodes and TaskTrackers.

I'm running into a problem with using the JobTracker web interface.

I can see the two .jsp files (jobdetails.jsp and jobtracker.jsp) when I point my browser at http://master:50030, but when I actually try to run one of the JSPs (e.g. http://master:50030/jobdetails.jsp) I get a 500 error.

The nutch-crawler-jobtracker-main1.log file on the master tells me that Jetty wasn't able to compile the .jsp because of a classpath problem. The relevant portion of the log says:

060114 110818 SEVERE Javac exception
Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK

[snip]

I've verified that JAVA_HOME is set to /usr/java/jre1.5.0_05

Is the problem because this isn't a full JDK?

What's confusing to me is that the classpath dumped by Jetty in the log looks like:

classpath=/tmp/Jetty__50030___24406:/usr/java/jre1.5.0_05/lib/ext/localedata.jar:/usr/java/jre1.5.0_05/lib/ext/sunpkcs11.jar [snip]

So obviously somebody is using JAVA_HOME to build the path to these .jar files.

But JAVA_HOME (the top-level path, ie /usr/java/jre1.5.0_05) isn't a member of this classpath.

Any help would be appreciated!

Thanks,

-- Ken
--
Ken Krugler
Krugle, Inc.
+1 530-470-9200

Reply via email to