Mithila Nagendra wrote:
I tried dropping the jar files into the lib. It still doesnt work.. The following is how the lib looks after the new files were put in:[EMAIL PROTECTED] hadoop-0.17.2.1]$ cd bin [EMAIL PROTECTED] bin]$ ls hadoop hadoop-daemon.sh rcc start-all.sh start-dfs.sh stop-all.sh stop-dfs.sh hadoop-config.sh hadoop-daemons.sh slaves.sh start-balancer.sh start-mapred.sh stop-balancer.sh stop-mapred.sh [EMAIL PROTECTED] bin]$ cd .. [EMAIL PROTECTED] hadoop-0.17.2.1]$ mv commons-logging-1.1.1/* lib [EMAIL PROTECTED] hadoop-0.17.2.1]$ cd lib [EMAIL PROTECTED] lib]$ ls commons-cli-2.0-SNAPSHOT.jar commons-logging-1.1.1-javadoc.jar commons-logging-tests.jar junit-3.8.1.jar log4j-1.2.13.jar site commons-codec-1.3.jar commons-logging-1.1.1-sources.jar jets3t-0.5.0.jar junit-3.8.1.LICENSE.txt native xmlenc-0.52.jar commons-httpclient-3.0.1.jar commons-logging-adapters-1.1.1.jar jetty-5.1.4.jar kfs-0.1.jar NOTICE.txt commons-logging-1.0.4.jar commons-logging-api-1.0.4.jar jetty-5.1.4.LICENSE.txt kfs-0.1.LICENSE.txt RELEASE-NOTES.txt commons-logging-1.1.1.jar commons-logging-api-1.1.1.jar jetty-ext LICENSE.txt servlet-api.jar
OK, you now have two copies of commons-logging in there. I would detele the -1.0.4 version and the -api and -sources JARs.
But I don't think that is the root cause of this problem. Are you running on a linux system that has commons-logging installed as an RPM or .deb package? Because that could be making a real mess of your classpath. The error your are seeing implies that log4j isnt there or it won't load. And as log4j is there, it looks like a classloader problem of some sort. These are tractable, but they are hard to track down and it is only on your system(s) that it exists. There's not much that can be done remotely.
-steve
