hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mithila Nagendra" <mnage...@asu.edu>
Subject Re: Hadoop Installation
Date Mon, 24 Nov 2008 17:06:26 GMT
Hey Steve

Out of the following which one do I remove - just making sure.. I got rid
of  commons-logging-1.0.4.jar

commons-logging-1.1.1-sources.jar commons-logging-1.1.1-sources.jar


On Mon, Nov 24, 2008 at 6:32 PM, Steve Loughran <stevel@apache.org> wrote:

> 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:
>> [mithila@node01 hadoop-]$ cd bin
>> [mithila@node01 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
>> [mithila@node01 bin]$ cd ..
>> [mithila@node01 hadoop-]$ mv commons-logging-1.1.1/* lib
>> [mithila@node01 hadoop-]$ cd lib
>> [mithila@node01 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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message