flume-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ankul rastogi <ankul.rast...@gmail.com>
Subject Re: Flume agent failure
Date Tue, 03 Jul 2012 17:49:56 GMT
Hi,

I had the same problem.
The quick solution that worked for me was to copy the *hadoop-core-1.0.3.jar
* to <flume-installation>/lib folder*. *You can find this jar in your
hadoop installation directory.

On Tue, Jul 3, 2012 at 10:14 PM, Mike Percy <mpercy@cloudera.com> wrote:

> On Mon, Jul 2, 2012 at 12:11 AM, vijay k <k.vijay52@gmail.com> wrote:
>
>>
>>
>> root@md-trngpoc1:/usr/local/flume_dir/flume/flume-1.2.0-incubating-SNAPSHOT#
>> bin/flume-ng agent -n agent1 -c conf -f conf/agent1.conf
>> Info: Sourcing environment configuration script
>> /usr/local/flume_dir/flume/flume-1.2.0-incubating-SNAPSHOT/conf/flume-env.sh
>> Info: Including Hadoop libraries found via (/usr/local/hadoop/bin/hadoop)
>> for HDFS access
>> + exec /usr/lib/jvm/java-6-sun-1.6.0.26/jre/bin/java -Xms100m -Xmx200m
>> -cp
>> '/usr/local/flume_dir/flume/flume-1.2.0-incubating-SNAPSHOT/conf:/usr/local/flume_dir/flume/flume-1.2.0-incubating-SNAPSHOT/lib/*:/usr/local/flume_dir/flume/flume-1.2.0-incubating-SNAPSHOT/conf'
>> -Djava.library.path=:/usr/local/hadoop/bin/../lib/native/Linux-i386-32
>> org.apache.flume.node.Application -n agent1 -f conf/agent1.conf
>>
>
> This is really strange. Your java.library.path is set to
> /usr/local/hadoop/lib/native/Linux-i386-32 but for some reason the output
> of "hadoop classpath" has not made it into your classpath. I've never seen
> that combination before - usually both are there or both are missing.
> That's because the same hadoop binary is used for both cases. Are you on a
> 32-bit OS? I don't know if anyone has ever tested Flume on a 32-bit OS.
>
> If you can post the output of the following 6 commands, it might give us
> more to go on:
>
> which hadoop
> echo $HADOOP_HOME
> hadoop classpath
> which java
> echo $JAVA_HOME
> java -version
>
> If you are fluent in shell scripting, you can also trace the bin/flume-ng
> script and see where it's going wrong. Or just invoke it as:
>
>   bash -x bin/flume-ng agent -n agent1 -c conf -f conf/agent1.conf
>
> And post the output of that as well (it will be quite long).
>
> Regards,
> Mike
>
>

Mime
View raw message