Hive, mail # user - RE: namenode starting error

namenode starting error

soham sardar 2012-06-20, 09:22

the thing is i have updated my JAVA_HOME in both .bashrc and hadoop-env.sh
now the problem is when i try
jps is the output is

6113 NodeManager
6799 DataNode
7562 Jps
7104 SecondaryNameNode
5728 ResourceManager

and now except namenode ,all other nodes are working and when i try to give

hadoop fs -ls

hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin$ hadoop fs -ls
12/06/20 14:45:14 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
12/06/20 14:45:15 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 1 time(s).
12/06/20 14:45:16 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 2 time(s).
12/06/20 14:45:17 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 3 time(s).
12/06/20 14:45:18 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 4 time(s).
12/06/20 14:45:19 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 5 time(s).
12/06/20 14:45:20 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 6 time(s).
12/06/20 14:45:21 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 7 time(s).
12/06/20 14:45:22 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 8 time(s).
12/06/20 14:45:23 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 9 time(s).
ls: Call From XPS-L501X/127.0.1.1 to localhost:54310 failed on
connection exception: java.net.ConnectException: Connection refused;
For more details see: http://wiki.apache.org/hadoop/ConnectionRefused

could u temme why this error is coming ?????????

Re: namenode starting error

Mohammad Tariq 2012-06-20, 09:26

change the line "127.0.1.1" in your /etc/hosts file to
"127.0.0.1"..Also check if there is any problem with the configuration
properties.

Regards,
Mohammad Tariq
On Wed, Jun 20, 2012 at 2:52 PM, soham sardar <[EMAIL PROTECTED]> wrote:
> the thing is i have updated my JAVA_HOME in both .bashrc and hadoop-env.sh
>
>
> now the problem is when i try
> jps is the output is
>
> 6113 NodeManager
> 6799 DataNode
> 7562 Jps
> 7104 SecondaryNameNode
> 5728 ResourceManager
>
> and now except namenode ,all other nodes are working and when i try to give
>
> hadoop fs -ls
>
> hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin$ hadoop fs -ls
> 12/06/20 14:45:14 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 0 time(s).
> 12/06/20 14:45:15 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 1 time(s).
> 12/06/20 14:45:16 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 2 time(s).
> 12/06/20 14:45:17 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 3 time(s).
> 12/06/20 14:45:18 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 4 time(s).
> 12/06/20 14:45:19 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 5 time(s).
> 12/06/20 14:45:20 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 6 time(s).
> 12/06/20 14:45:21 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 7 time(s).
> 12/06/20 14:45:22 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 8 time(s).
> 12/06/20 14:45:23 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 9 time(s).
> ls: Call From XPS-L501X/127.0.1.1 to localhost:54310 failed on
> connection exception: java.net.ConnectException: Connection refused;
> For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
>
> could u temme why this error is coming ?????????

Re: namenode starting error

soham sardar 2012-06-20, 09:38

No i guess it still doesnt serve the purpose actually i mean the error is
hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/etc/hadoop$
hadoop fs -ls
12/06/20 15:03:51 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
12/06/20 15:03:52 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 1 time(s).
12/06/20 15:03:53 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 2 time(s).
12/06/20 15:03:54 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 3 time(s).
12/06/20 15:03:55 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 4 time(s).
12/06/20 15:03:56 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 5 time(s).
12/06/20 15:03:57 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 6 time(s).
12/06/20 15:03:58 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 7 time(s).
12/06/20 15:03:59 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 8 time(s).
12/06/20 15:04:00 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 9 time(s).
ls: Call From XPS-L501X/127.0.0.1 to localhost:54310 failed on
connection exception: java.net.ConnectException: Connection refused;
For more details see: http://wiki.apache.org/hadoop/ConnectionRefused

can u just specify what exactly the configurations i must check that
might cause this problem
till now i have added properties into core-site.xml hdfs-site.xml
yarn-site.xml.......

On Wed, Jun 20, 2012 at 2:56 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
> change the line "127.0.1.1" in your /etc/hosts file to
> "127.0.0.1"..Also check if there is any problem with the configuration
> properties.
>
> Regards,
> Mohammad Tariq
>
>
> On Wed, Jun 20, 2012 at 2:52 PM, soham sardar <[EMAIL PROTECTED]> wrote:
>> the thing is i have updated my JAVA_HOME in both .bashrc and hadoop-env.sh
>>
>>
>> now the problem is when i try
>> jps is the output is
>>
>> 6113 NodeManager
>> 6799 DataNode
>> 7562 Jps
>> 7104 SecondaryNameNode
>> 5728 ResourceManager
>>
>> and now except namenode ,all other nodes are working and when i try to give
>>
>> hadoop fs -ls
>>
>> hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin$ hadoop fs -ls
>> 12/06/20 14:45:14 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 0 time(s).
>> 12/06/20 14:45:15 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 1 time(s).
>> 12/06/20 14:45:16 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 2 time(s).
>> 12/06/20 14:45:17 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 3 time(s).
>> 12/06/20 14:45:18 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 4 time(s).
>> 12/06/20 14:45:19 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 5 time(s).
>> 12/06/20 14:45:20 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 6 time(s).
>> 12/06/20 14:45:21 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 7 time(s).
>> 12/06/20 14:45:22 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 8 time(s).
>> 12/06/20 14:45:23 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 9 time(s).
>> ls: Call From XPS-L501X/127.0.1.1 to localhost:54310 failed on
>> connection exception: java.net.ConnectException: Connection refused;
>> For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
>>
>> could u temme why this error is coming ?????????

Re: namenode starting error

Mohammad Tariq 2012-06-20, 09:50

this is because you are you are not able to contact the namenode as it
is not running.not only -ls, none of the Hdfs command will work in
such a situation..was your NN stopped after getting started, or it
didn't start even once??Can you paste your logs here??

Regards,
Mohammad Tariq
On Wed, Jun 20, 2012 at 3:08 PM, soham sardar <[EMAIL PROTECTED]> wrote:
> No i guess it still doesnt serve the purpose actually i mean the error is
> hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/etc/hadoop$
> hadoop fs -ls
> 12/06/20 15:03:51 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 0 time(s).
> 12/06/20 15:03:52 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 1 time(s).
> 12/06/20 15:03:53 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 2 time(s).
> 12/06/20 15:03:54 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 3 time(s).
> 12/06/20 15:03:55 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 4 time(s).
> 12/06/20 15:03:56 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 5 time(s).
> 12/06/20 15:03:57 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 6 time(s).
> 12/06/20 15:03:58 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 7 time(s).
> 12/06/20 15:03:59 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 8 time(s).
> 12/06/20 15:04:00 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 9 time(s).
> ls: Call From XPS-L501X/127.0.0.1 to localhost:54310 failed on
> connection exception: java.net.ConnectException: Connection refused;
> For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
>
> can u just specify what exactly the configurations i must check that
> might cause this problem
> till now i have added properties into core-site.xml hdfs-site.xml
> yarn-site.xml.......
>
> On Wed, Jun 20, 2012 at 2:56 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
>> change the line "127.0.1.1" in your /etc/hosts file to
>> "127.0.0.1"..Also check if there is any problem with the configuration
>> properties.
>>
>> Regards,
>> Mohammad Tariq
>>
>>
>> On Wed, Jun 20, 2012 at 2:52 PM, soham sardar <[EMAIL PROTECTED]> wrote:
>>> the thing is i have updated my JAVA_HOME in both .bashrc and hadoop-env.sh
>>>
>>>
>>> now the problem is when i try
>>> jps is the output is
>>>
>>> 6113 NodeManager
>>> 6799 DataNode
>>> 7562 Jps
>>> 7104 SecondaryNameNode
>>> 5728 ResourceManager
>>>
>>> and now except namenode ,all other nodes are working and when i try to give
>>>
>>> hadoop fs -ls
>>>
>>> hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin$ hadoop fs -ls
>>> 12/06/20 14:45:14 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 0 time(s).
>>> 12/06/20 14:45:15 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 1 time(s).
>>> 12/06/20 14:45:16 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 2 time(s).
>>> 12/06/20 14:45:17 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 3 time(s).
>>> 12/06/20 14:45:18 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 4 time(s).
>>> 12/06/20 14:45:19 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 5 time(s).
>>> 12/06/20 14:45:20 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 6 time(s).
>>> 12/06/20 14:45:21 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 7 time(s).
>>> 12/06/20 14:45:22 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 8 time(s).

Re: namenode starting error

soham sardar 2012-06-20, 09:56

NO IT DIDNT START EVEN ONCE
AND YEA I TRIED FORMATTING IT , I DUNNO WETHER IT REALLY GOT FORMATTED .........

2012-06-19 16:48:36,908 INFO
org.apache.hadoop.hdfs.server.namenode.NameNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = XPS-L501X/127.0.1.1
STARTUP_MSG: args = []
STARTUP_MSG: version = 2.0.0-cdh4.0.0
STARTUP_MSG: classpath /home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/etc/hadoop:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-json-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/xmlenc-0.52.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jsp-api-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/snappy-java-1.0.3.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/slf4j-log4j12-1.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/kfs-0.3.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jaxb-api-2.2.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-logging-api-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-digester-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jettison-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-el-1.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-core-asl-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/hadoop-auth-2.0.0-cdh4.0.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-jaxrs-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jaxb-impl-2.2.3-1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-codec-1.4.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/guava-11.0.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jasper-compiler-5.5.23.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-lang-2.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-configuration-1.6.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/servlet-api-2.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/activation-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/log4j-1.2.15.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-collections-3.2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-mapper-asl-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-beanutils-core-1.8.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jline-0.9.94.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/avro-1.5.4.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/slf4j-api-1.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jasper-runtime-5.5.23.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/oro-2.0.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-logging-1.1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-httpclient-3.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/stax-api-1.0.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/json-simple-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-core-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-math-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/paranamer-2.3.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/aspectjrt-1.6.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/core-3.1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/protobuf-java-2.4.0a.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-cli-1.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-net-3.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-io-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jets3t-0.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-server-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/zookeeper-3.4.3-cdh4.0.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/asm-3.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jetty-util-6.1.26.cloudera.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-beanutils-1.7.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jetty-6.1.26.cloudera.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-xc-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jsr305-1.3.9.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jsch-0.1.42.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/hadoop-common-2.0.0-cdh4.0.0-test-sources.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/hadoop-common-2.0.0-cdh4.0.0-sources.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/hadoop-common-2.0.0-cdh4.0.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/hadoop-common-2.0.0-cdh4.0.0-tests.jar:/contrib/capacity-scheduler/*.jar:/contrib/capacity-scheduler/*.jar:/contrib/capacity-scheduler/*.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/hdfs:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/hdfs/lib/snappy-java-1.0.3.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/hdfs/lib/

Re: namenode starting error

Mohammad Tariq 2012-06-20, 10:07

Add the following properties in your config files and then do a fresh
format.and then restart the processes :

1- In core-site.xml file :
<property>
   <name>hadoop.tmp.dir</name>
   <value>/home/mohammad/hdfs/temp(some location on your disk)</value>
</property>

2- In hdfs-site.xml :
<property>
   <name>dfs.name.dir</name>
   <value>/home/mohammad/hdfs/name(some location on your disk)</value>
</property>
<property>
   <name>dfs.data.dir</name>
   <value>/home/mohammad/hdfs/data(some location on your disk)</value>
</property>

It should work.
Regards,
   Mohammad Tariq
On Wed, Jun 20, 2012 at 3:26 PM, soham sardar <[EMAIL PROTECTED]> wrote:
> NO IT DIDNT START EVEN ONCE
> AND YEA I TRIED FORMATTING IT , I DUNNO WETHER IT REALLY GOT FORMATTED .........
>
> 2012-06-19 16:48:36,908 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: STARTUP_MSG:
> /************************************************************
> STARTUP_MSG: Starting NameNode
> STARTUP_MSG: host = XPS-L501X/127.0.1.1
> STARTUP_MSG: args = []
> STARTUP_MSG: version = 2.0.0-cdh4.0.0
> STARTUP_MSG: classpath > /home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/etc/hadoop:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-json-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/xmlenc-0.52.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jsp-api-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/snappy-java-1.0.3.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/slf4j-log4j12-1.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/kfs-0.3.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jaxb-api-2.2.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-logging-api-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-digester-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jettison-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-el-1.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-core-asl-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/hadoop-auth-2.0.0-cdh4.0.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-jaxrs-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jaxb-impl-2.2.3-1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-codec-1.4.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/guava-11.0.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jasper-compiler-5.5.23.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-lang-2.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-configuration-1.6.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/servlet-api-2.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/activation-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/log4j-1.2.15.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-collections-3.2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-mapper-asl-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-beanutils-core-1.8.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jline-0.9.94.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/avro-1.5.4.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/slf4j-api-1.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jasper-runtime-5.5.23.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/oro-2.0.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-logging-1.1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-httpclient-3.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/stax-api-1.0.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/json-simple-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-core-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-math-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/paranamer-2.3.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/aspectjrt-1.6.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/core-3.1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/protobuf-java-2.4.0a.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-cli-1.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-net-3.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-io-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jets3t-0.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-server-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/zookeeper-3.4.3-cdh4.0.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/asm-3.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jetty-util-6.1.26.cloudera.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-beanutils-1.7.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jetty-6.1.26.cloudera.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-xc-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jsr305-1.3.9.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jsch-0.1.42.jar:/

Re: namenode starting error

praveenesh kumar 2012-06-20, 12:23

Is your hadoop-datastore directory is created and having proper permissions?
Also, Are you sure you have executed --"hadoop namenode -format" command
before starting hadoop ?

Regards,
Praveenesh

On Wed, Jun 20, 2012 at 3:37 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:

> Add the following properties in your config files and then do a fresh
> format.and then restart the processes :
>
> 1- In core-site.xml file :
> <property>
> <name>hadoop.tmp.dir</name>
> <value>/home/mohammad/hdfs/temp(some location on your
> disk)</value>
> </property>
>
> 2- In hdfs-site.xml :
> <property>
> <name>dfs.name.dir</name>
> <value>/home/mohammad/hdfs/name(some location on your
> disk)</value>
> </property>
> <property>
> <name>dfs.data.dir</name>
> <value>/home/mohammad/hdfs/data(some location on your
> disk)</value>
> </property>
>
> It should work.
> Regards,
> Mohammad Tariq
>
>
> On Wed, Jun 20, 2012 at 3:26 PM, soham sardar <[EMAIL PROTECTED]>
> wrote:
> > NO IT DIDNT START EVEN ONCE
> > AND YEA I TRIED FORMATTING IT , I DUNNO WETHER IT REALLY GOT FORMATTED
> .........
> >
> > 2012-06-19 16:48:36,908 INFO
> > org.apache.hadoop.hdfs.server.namenode.NameNode: STARTUP_MSG:
> > /************************************************************
> > STARTUP_MSG: Starting NameNode
> > STARTUP_MSG: host = XPS-L501X/127.0.1.1
> > STARTUP_MSG: args = []
> > STARTUP_MSG: version = 2.0.0-cdh4.0.0
> > STARTUP_MSG: classpath > >
> /home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/etc/hadoop:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-json-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/xmlenc-0.52.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jsp-api-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/snappy-java-1.0.3.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/slf4j-log4j12-1.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/kfs-0.3.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jaxb-api-2.2.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-logging-api-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-digester-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jettison-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-el-1.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-core-asl-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/hadoop-auth-2.0.0-cdh4.0.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-jaxrs-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jaxb-impl-2.2.3-1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-codec-1.4.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/guava-11.0.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jasper-compiler-5.5.23.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-lang-2.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-configuration-1.6.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/servlet-api-2.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/activation-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/log4j-1.2.15.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-collections-3.2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jackson-mapper-asl-1.8.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-beanutils-core-1.8.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jline-0.9.94.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/avro-1.5.4.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/slf4j-api-1.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jasper-runtime-5.5.23.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/oro-2.0.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-logging-1.1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-httpclient-3.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/stax-api-1.0.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/json-simple-1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-core-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-math-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/paranamer-2.3.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/aspectjrt-1.6.5.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/core-3.1.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/protobuf-java-2.4.0a.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-cli-1.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-net-3.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/commons-io-2.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jets3t-0.6.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jersey-server-1.8.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/zookeeper-3.4.3-cdh4.0.0.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/asm-3.2.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/common/lib/jetty-util-6.1.26.cloudera.1.jar:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/share/hadoop/comm

Re: namenode starting error

soham sardar 2012-06-21, 07:23

I added the conf given by Mohammad to core site and hdfs site xmls and
i tried looking at the logs and then
/var/log/hadoop-0.20
i checked that there are just the out files and the log files for
secondary namenode , datanode , jobtracker and tasktracker
also when i try to run
hadoop dfs -ls

the output is
soham@XPS-L501X:/var/log/hadoop-0.20$ hadoop dfs -ls
DEPRECATED: Use of this script to execute hdfs command is deprecated.
Instead use the hdfs command for it.

ls: `.': No such file or directory

and when i try to run
hadoop namenode

2/06/21 12:52:46 INFO namenode.FSNamesystem: fsOwner soham (auth:SIMPLE)
12/06/21 12:52:46 INFO namenode.FSNamesystem: supergroup = supergroup
12/06/21 12:52:46 INFO namenode.FSNamesystem: isPermissionEnabled = false
12/06/21 12:52:46 INFO namenode.FSNamesystem: HA Enabled: false
12/06/21 12:52:46 INFO namenode.FSNamesystem: Append Enabled: true
12/06/21 12:52:47 INFO namenode.NameNode: Caching file names occuring
more than 10 times
12/06/21 12:52:47 INFO common.Storage: Cannot lock storage /tmp/name.
The directory is already locked.
12/06/21 12:52:47 INFO impl.MetricsSystemImpl: Stopping NameNode
metrics system...
12/06/21 12:52:47 INFO impl.MetricsSystemImpl: NameNode metrics system stopped.
12/06/21 12:52:47 INFO impl.MetricsSystemImpl: NameNode metrics system
shutdown complete.
12/06/21 12:52:47 ERROR namenode.NameNode: Exception in namenode join
java.io.IOException: Cannot lock storage /tmp/name. The directory is
already locked.
at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.lock(Storage.java:580)
at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.analyzeStorage(Storage.java:429)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:264)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:180)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)
12/06/21 12:52:47 INFO namenode.NameNode: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at XPS-L501X/127.0.0.1
************************************************************/

On Wed, Jun 20, 2012 at 5:53 PM, praveenesh kumar <[EMAIL PROTECTED]> wrote:
> Is your hadoop-datastore directory is created and having proper permissions?
> Also, Are you sure you have executed --"hadoop namenode -format" command
> before starting hadoop ?
>
> Regards,
> Praveenesh
>
> On Wed, Jun 20, 2012 at 3:37 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
>>
>> Add the following properties in your config files and then do a fresh
>> format.and then restart the processes :
>>
>> 1- In core-site.xml file :
>> <property>
>> <name>hadoop.tmp.dir</name>
>> <value>/home/mohammad/hdfs/temp(some location on your
>> disk)</value>
>> </property>
>>
>> 2- In hdfs-site.xml :
>> <property>
>> <name>dfs.name.dir</name>
>> <value>/home/mohammad/hdfs/name(some location on your
>> disk)</value>
>> </property>
>> <property>
>> <name>dfs.data.dir</name>
>> <value>/home/mohammad/hdfs/data(some location on your
>> disk)</value>
>> </property>
>>
>> It should work.
>> Regards,
>> Mohammad Tariq
>>
>>
>> On Wed, Jun 20, 2012 at 3:26 PM, soham sardar <[EMAIL PROTECTED]>

Re: namenode starting error

Mohammad Tariq 2012-06-21, 07:30

Have you formatted the namenode after adding those properties??If not
then do it. Also change the permissions of all the directories to 777.
And use commands with fs and not dfs, like :
$ hadoop fs - ls /

Regards,
Mohammad Tariq
On Thu, Jun 21, 2012 at 12:53 PM, soham sardar
<[EMAIL PROTECTED]> wrote:
> I added the conf given by Mohammad to core site and hdfs site xmls and
> i tried looking at the logs and then
> /var/log/hadoop-0.20
> i checked that there are just the out files and the log files for
> secondary namenode , datanode , jobtracker and tasktracker
> also when i try to run
> hadoop dfs -ls
>
> the output is
> soham@XPS-L501X:/var/log/hadoop-0.20$ hadoop dfs -ls
> DEPRECATED: Use of this script to execute hdfs command is deprecated.
> Instead use the hdfs command for it.
>
> ls: `.': No such file or directory
>
> and when i try to run
> hadoop namenode
>
> 2/06/21 12:52:46 INFO namenode.FSNamesystem: fsOwner > soham (auth:SIMPLE)
> 12/06/21 12:52:46 INFO namenode.FSNamesystem: supergroup = supergroup
> 12/06/21 12:52:46 INFO namenode.FSNamesystem: isPermissionEnabled = false
> 12/06/21 12:52:46 INFO namenode.FSNamesystem: HA Enabled: false
> 12/06/21 12:52:46 INFO namenode.FSNamesystem: Append Enabled: true
> 12/06/21 12:52:47 INFO namenode.NameNode: Caching file names occuring
> more than 10 times
> 12/06/21 12:52:47 INFO common.Storage: Cannot lock storage /tmp/name.
> The directory is already locked.
> 12/06/21 12:52:47 INFO impl.MetricsSystemImpl: Stopping NameNode
> metrics system...
> 12/06/21 12:52:47 INFO impl.MetricsSystemImpl: NameNode metrics system stopped.
> 12/06/21 12:52:47 INFO impl.MetricsSystemImpl: NameNode metrics system
> shutdown complete.
> 12/06/21 12:52:47 ERROR namenode.NameNode: Exception in namenode join
> java.io.IOException: Cannot lock storage /tmp/name. The directory is
> already locked.
> at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.lock(Storage.java:580)
> at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.analyzeStorage(Storage.java:429)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:264)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:180)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)
> 12/06/21 12:52:47 INFO namenode.NameNode: SHUTDOWN_MSG:
> /************************************************************
> SHUTDOWN_MSG: Shutting down NameNode at XPS-L501X/127.0.0.1
> ************************************************************/
>
>
>
>
>
>
>
>
>
>
>
> On Wed, Jun 20, 2012 at 5:53 PM, praveenesh kumar <[EMAIL PROTECTED]> wrote:
>> Is your hadoop-datastore directory is created and having proper permissions?
>> Also, Are you sure you have executed --"hadoop namenode -format" command
>> before starting hadoop ?
>>
>> Regards,
>> Praveenesh
>>
>> On Wed, Jun 20, 2012 at 3:37 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
>>>
>>> Add the following properties in your config files and then do a fresh
>>> format.and then restart the processes :
>>>
>>> 1- In core-site.xml file :
>>> <property>
>>> <name>hadoop.tmp.dir</name>

Re: namenode starting error

soham sardar 2012-06-21, 08:53

Whenver i try to do
hadoop namenode

12/06/21 14:21:54 WARN mortbay.log: Can't reuse
/tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08, using
/tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08_8403409681665615259
12/06/21 14:21:54 INFO mortbay.log: Started SelectChannelConnector@0.0.0.0:50070
12/06/21 14:21:54 INFO namenode.NameNode: Web-server up at: 0.0.0.0:50070
12/06/21 14:21:54 INFO ipc.Server: IPC Server Responder: starting
12/06/21 14:21:54 INFO ipc.Server: IPC Server listener on 54310: starting
12/06/21 14:21:54 INFO namenode.NameNode: NameNode up at:
localhost/127.0.0.1:54310
12/06/21 14:21:54 INFO namenode.FSNamesystem: Starting services
required for active state
there are a series of process and then ir stops in the last line of
the above error snippet ..
can someone help me with this ?

On Thu, Jun 21, 2012 at 1:00 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
> Have you formatted the namenode after adding those properties??If not
> then do it. Also change the permissions of all the directories to 777.
> And use commands with fs and not dfs, like :
> $ hadoop fs - ls /
>
> Regards,
> Mohammad Tariq
>
>
> On Thu, Jun 21, 2012 at 12:53 PM, soham sardar
> <[EMAIL PROTECTED]> wrote:
>> I added the conf given by Mohammad to core site and hdfs site xmls and
>> i tried looking at the logs and then
>> /var/log/hadoop-0.20
>> i checked that there are just the out files and the log files for
>> secondary namenode , datanode , jobtracker and tasktracker
>> also when i try to run
>> hadoop dfs -ls
>>
>> the output is
>> soham@XPS-L501X:/var/log/hadoop-0.20$ hadoop dfs -ls
>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
>> Instead use the hdfs command for it.
>>
>> ls: `.': No such file or directory
>>
>> and when i try to run
>> hadoop namenode
>>
>> 2/06/21 12:52:46 INFO namenode.FSNamesystem: fsOwner >> soham (auth:SIMPLE)
>> 12/06/21 12:52:46 INFO namenode.FSNamesystem: supergroup = supergroup
>> 12/06/21 12:52:46 INFO namenode.FSNamesystem: isPermissionEnabled = false
>> 12/06/21 12:52:46 INFO namenode.FSNamesystem: HA Enabled: false
>> 12/06/21 12:52:46 INFO namenode.FSNamesystem: Append Enabled: true
>> 12/06/21 12:52:47 INFO namenode.NameNode: Caching file names occuring
>> more than 10 times
>> 12/06/21 12:52:47 INFO common.Storage: Cannot lock storage /tmp/name.
>> The directory is already locked.
>> 12/06/21 12:52:47 INFO impl.MetricsSystemImpl: Stopping NameNode
>> metrics system...
>> 12/06/21 12:52:47 INFO impl.MetricsSystemImpl: NameNode metrics system stopped.
>> 12/06/21 12:52:47 INFO impl.MetricsSystemImpl: NameNode metrics system
>> shutdown complete.
>> 12/06/21 12:52:47 ERROR namenode.NameNode: Exception in namenode join
>> java.io.IOException: Cannot lock storage /tmp/name. The directory is
>> already locked.
>> at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.lock(Storage.java:580)
>> at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.analyzeStorage(Storage.java:429)
>> at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:264)
>> at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:180)
>> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
>> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
>> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)

Re: namenode starting error

soham sardar 2012-06-21, 08:55

And mohammad i formatted the namenode and then ran the command
hduser@XPS-L501X:~/cloudera/hadoop-2.0.0-cdh4.0.0$ hadoop dfs -ls
DEPRECATED: Use of this script to execute hdfs command is deprecated.
Instead use the hdfs command for it.

12/06/21 14:23:56 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
12/06/21 14:23:57 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 1 time(s).
12/06/21 14:23:58 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 2 time(s).
12/06/21 14:23:59 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 3 time(s).
12/06/21 14:24:00 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 4 time(s).
12/06/21 14:24:01 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 5 time(s).
12/06/21 14:24:02 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 6 time(s).
12/06/21 14:24:03 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 7 time(s).
12/06/21 14:24:04 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 8 time(s).
12/06/21 14:24:05 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 9 time(s).
ls: Call From XPS-L501X/127.0.0.1 to localhost:54310 failed on
connection exception: java.net.ConnectException: Connection refused;
For more details see: http://wiki.apache.org/hadoop/ConnectionRefused

??

On Thu, Jun 21, 2012 at 2:23 PM, soham sardar <[EMAIL PROTECTED]> wrote:
> Whenver i try to do
> hadoop namenode
>
> 12/06/21 14:21:54 WARN mortbay.log: Can't reuse
> /tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08, using
> /tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08_8403409681665615259
> 12/06/21 14:21:54 INFO mortbay.log: Started SelectChannelConnector@0.0.0.0:50070
> 12/06/21 14:21:54 INFO namenode.NameNode: Web-server up at: 0.0.0.0:50070
> 12/06/21 14:21:54 INFO ipc.Server: IPC Server Responder: starting
> 12/06/21 14:21:54 INFO ipc.Server: IPC Server listener on 54310: starting
> 12/06/21 14:21:54 INFO namenode.NameNode: NameNode up at:
> localhost/127.0.0.1:54310
> 12/06/21 14:21:54 INFO namenode.FSNamesystem: Starting services
> required for active state
>
>
> there are a series of process and then ir stops in the last line of
> the above error snippet ..
> can someone help me with this ?
>
> On Thu, Jun 21, 2012 at 1:00 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
>> Have you formatted the namenode after adding those properties??If not
>> then do it. Also change the permissions of all the directories to 777.
>> And use commands with fs and not dfs, like :
>> $ hadoop fs - ls /
>>
>> Regards,
>> Mohammad Tariq
>>
>>
>> On Thu, Jun 21, 2012 at 12:53 PM, soham sardar
>> <[EMAIL PROTECTED]> wrote:
>>> I added the conf given by Mohammad to core site and hdfs site xmls and
>>> i tried looking at the logs and then
>>> /var/log/hadoop-0.20
>>> i checked that there are just the out files and the log files for
>>> secondary namenode , datanode , jobtracker and tasktracker
>>> also when i try to run
>>> hadoop dfs -ls
>>>
>>> the output is
>>> soham@XPS-L501X:/var/log/hadoop-0.20$ hadoop dfs -ls
>>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
>>> Instead use the hdfs command for it.
>>>
>>> ls: `.': No such file or directory
>>>
>>> and when i try to run
>>> hadoop namenode
>>>
>>> 2/06/21 12:52:46 INFO namenode.FSNamesystem: fsOwner >>> soham (auth:SIMPLE)
>>> 12/06/21 12:52:46 INFO namenode.FSNamesystem: supergroup = supergroup
>>> 12/06/21 12:52:46 INFO namenode.FSNamesystem: isPermissionEnabled = false
>>> 12/06/21 12:52:46 INFO namenode.FSNamesystem: HA Enabled: false
>>> 12/06/21 12:52:46 INFO namenode.FSNamesystem: Append Enabled: true
>>> 12/06/21 12:52:47 INFO namenode.NameNode: Caching file names occuring

Re: namenode starting error

shashwat shriparv 2012-06-21, 11:42

Dear Soham can you send the content of your /etc/hosts file and
/etc/hostname file contents.... ??

Regards

Shashwat Shriparv
On Thu, Jun 21, 2012 at 2:25 PM, soham sardar <[EMAIL PROTECTED]>wrote:

> And mohammad i formatted the namenode and then ran the command
> hduser@XPS-L501X:~/cloudera/hadoop-2.0.0-cdh4.0.0$ hadoop dfs -ls
>
>
> DEPRECATED: Use of this script to execute hdfs command is deprecated.
> Instead use the hdfs command for it.
>
> 12/06/21 14:23:56 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 0 time(s).
> 12/06/21 14:23:57 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 1 time(s).
> 12/06/21 14:23:58 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 2 time(s).
> 12/06/21 14:23:59 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 3 time(s).
> 12/06/21 14:24:00 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 4 time(s).
> 12/06/21 14:24:01 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 5 time(s).
> 12/06/21 14:24:02 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 6 time(s).
> 12/06/21 14:24:03 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 7 time(s).
> 12/06/21 14:24:04 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 8 time(s).
> 12/06/21 14:24:05 INFO ipc.Client: Retrying connect to server:
> localhost/127.0.0.1:54310. Already tried 9 time(s).
> ls: Call From XPS-L501X/127.0.0.1 to localhost:54310 failed on
> connection exception: java.net.ConnectException: Connection refused;
> For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
>
> ??
>
> On Thu, Jun 21, 2012 at 2:23 PM, soham sardar <[EMAIL PROTECTED]>
> wrote:
> > Whenver i try to do
> > hadoop namenode
> >
> > 12/06/21 14:21:54 WARN mortbay.log: Can't reuse
> > /tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08, using
> > /tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08_8403409681665615259
> > 12/06/21 14:21:54 INFO mortbay.log: Started
> SelectChannelConnector@0.0.0.0:50070
> > 12/06/21 14:21:54 INFO namenode.NameNode: Web-server up at:
> 0.0.0.0:50070
> > 12/06/21 14:21:54 INFO ipc.Server: IPC Server Responder: starting
> > 12/06/21 14:21:54 INFO ipc.Server: IPC Server listener on 54310: starting
> > 12/06/21 14:21:54 INFO namenode.NameNode: NameNode up at:
> > localhost/127.0.0.1:54310
> > 12/06/21 14:21:54 INFO namenode.FSNamesystem: Starting services
> > required for active state
> >
> >
> > there are a series of process and then ir stops in the last line of
> > the above error snippet ..
> > can someone help me with this ?
> >
> > On Thu, Jun 21, 2012 at 1:00 PM, Mohammad Tariq <[EMAIL PROTECTED]>
> wrote:
> >> Have you formatted the namenode after adding those properties??If not
> >> then do it. Also change the permissions of all the directories to 777.
> >> And use commands with fs and not dfs, like :
> >> $ hadoop fs - ls /
> >>
> >> Regards,
> >> Mohammad Tariq
> >>
> >>
> >> On Thu, Jun 21, 2012 at 12:53 PM, soham sardar
> >> <[EMAIL PROTECTED]> wrote:
> >>> I added the conf given by Mohammad to core site and hdfs site xmls and
> >>> i tried looking at the logs and then
> >>> /var/log/hadoop-0.20
> >>> i checked that there are just the out files and the log files for
> >>> secondary namenode , datanode , jobtracker and tasktracker
> >>> also when i try to run
> >>> hadoop dfs -ls
> >>>
> >>> the output is
> >>> soham@XPS-L501X:/var/log/hadoop-0.20$ hadoop dfs -ls
> >>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
> >>> Instead use the hdfs command for it.
> >>>
> >>> ls: `.': No such file or directory
> >>>
> >>> and when i try to run
> >>> hadoop namenode
> >>>
> >>> 2/06/21 12:52:46 INFO namenode.FSNamesystem: fsOwner > >
∞
Shashwat Shriparv

Re: namenode starting error

shashwat shriparv 2012-06-21, 11:45

And also configuration files contents....

On Thu, Jun 21, 2012 at 5:12 PM, shashwat shriparv <
[EMAIL PROTECTED]> wrote:

> Dear Soham can you send the content of your /etc/hosts file and
> /etc/hostname file contents.... ??
>
>
>
> Regards
>
> Shashwat Shriparv
>
>
> On Thu, Jun 21, 2012 at 2:25 PM, soham sardar <[EMAIL PROTECTED]>wrote:
>
>> And mohammad i formatted the namenode and then ran the command
>> hduser@XPS-L501X:~/cloudera/hadoop-2.0.0-cdh4.0.0$ hadoop dfs -ls
>>
>>
>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
>> Instead use the hdfs command for it.
>>
>> 12/06/21 14:23:56 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 0 time(s).
>> 12/06/21 14:23:57 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 1 time(s).
>> 12/06/21 14:23:58 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 2 time(s).
>> 12/06/21 14:23:59 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 3 time(s).
>> 12/06/21 14:24:00 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 4 time(s).
>> 12/06/21 14:24:01 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 5 time(s).
>> 12/06/21 14:24:02 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 6 time(s).
>> 12/06/21 14:24:03 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 7 time(s).
>> 12/06/21 14:24:04 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 8 time(s).
>> 12/06/21 14:24:05 INFO ipc.Client: Retrying connect to server:
>> localhost/127.0.0.1:54310. Already tried 9 time(s).
>> ls: Call From XPS-L501X/127.0.0.1 to localhost:54310 failed on
>> connection exception: java.net.ConnectException: Connection refused;
>> For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
>>
>> ??
>>
>> On Thu, Jun 21, 2012 at 2:23 PM, soham sardar <[EMAIL PROTECTED]>
>> wrote:
>> > Whenver i try to do
>> > hadoop namenode
>> >
>> > 12/06/21 14:21:54 WARN mortbay.log: Can't reuse
>> > /tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08, using
>> > /tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08_8403409681665615259
>> > 12/06/21 14:21:54 INFO mortbay.log: Started
>> SelectChannelConnector@0.0.0.0:50070
>> > 12/06/21 14:21:54 INFO namenode.NameNode: Web-server up at:
>> 0.0.0.0:50070
>> > 12/06/21 14:21:54 INFO ipc.Server: IPC Server Responder: starting
>> > 12/06/21 14:21:54 INFO ipc.Server: IPC Server listener on 54310:
>> starting
>> > 12/06/21 14:21:54 INFO namenode.NameNode: NameNode up at:
>> > localhost/127.0.0.1:54310
>> > 12/06/21 14:21:54 INFO namenode.FSNamesystem: Starting services
>> > required for active state
>> >
>> >
>> > there are a series of process and then ir stops in the last line of
>> > the above error snippet ..
>> > can someone help me with this ?
>> >
>> > On Thu, Jun 21, 2012 at 1:00 PM, Mohammad Tariq <[EMAIL PROTECTED]>
>> wrote:
>> >> Have you formatted the namenode after adding those properties??If not
>> >> then do it. Also change the permissions of all the directories to 777.
>> >> And use commands with fs and not dfs, like :
>> >> $ hadoop fs - ls /
>> >>
>> >> Regards,
>> >> Mohammad Tariq
>> >>
>> >>
>> >> On Thu, Jun 21, 2012 at 12:53 PM, soham sardar
>> >> <[EMAIL PROTECTED]> wrote:
>> >>> I added the conf given by Mohammad to core site and hdfs site xmls and
>> >>> i tried looking at the logs and then
>> >>> /var/log/hadoop-0.20
>> >>> i checked that there are just the out files and the log files for
>> >>> secondary namenode , datanode , jobtracker and tasktracker
>> >>> also when i try to run
>> >>> hadoop dfs -ls
>> >>>
>> >>> the output is
>> >>> soham@XPS-L501X:/var/log/hadoop-0.20$ hadoop dfs -ls
>> >>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
∞
Shashwat Shriparv

Re: namenode starting error

Soham Sardar 2012-06-21, 11:51

hosts file
soham@XPS-L501X:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 XPS-L501X

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

hostname file
soham@XPS-L501X:~$ cat /etc/hostname
XPS-L501X
On Thu, Jun 21, 2012 at 5:15 PM, shashwat shriparv
<[EMAIL PROTECTED]> wrote:
> And also configuration files contents....
>
> On Thu, Jun 21, 2012 at 5:12 PM, shashwat shriparv
> <[EMAIL PROTECTED]> wrote:
>>
>> Dear Soham can you send the content of your /etc/hosts file and
>> /etc/hostname file contents.... ??
>>
>>
>>
>> Regards
>>
>> Shashwat Shriparv
>>
>>
>> On Thu, Jun 21, 2012 at 2:25 PM, soham sardar <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> And mohammad i formatted the namenode and then ran the command
>>> hduser@XPS-L501X:~/cloudera/hadoop-2.0.0-cdh4.0.0$ hadoop dfs -ls
>>>
>>>
>>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
>>> Instead use the hdfs command for it.
>>>
>>> 12/06/21 14:23:56 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 0 time(s).
>>> 12/06/21 14:23:57 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 1 time(s).
>>> 12/06/21 14:23:58 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 2 time(s).
>>> 12/06/21 14:23:59 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 3 time(s).
>>> 12/06/21 14:24:00 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 4 time(s).
>>> 12/06/21 14:24:01 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 5 time(s).
>>> 12/06/21 14:24:02 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 6 time(s).
>>> 12/06/21 14:24:03 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 7 time(s).
>>> 12/06/21 14:24:04 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 8 time(s).
>>> 12/06/21 14:24:05 INFO ipc.Client: Retrying connect to server:
>>> localhost/127.0.0.1:54310. Already tried 9 time(s).
>>> ls: Call From XPS-L501X/127.0.0.1 to localhost:54310 failed on
>>> connection exception: java.net.ConnectException: Connection refused;
>>> For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
>>>
>>> ??
>>>
>>> On Thu, Jun 21, 2012 at 2:23 PM, soham sardar <[EMAIL PROTECTED]>
>>> wrote:
>>> > Whenver i try to do
>>> > hadoop namenode
>>> >
>>> > 12/06/21 14:21:54 WARN mortbay.log: Can't reuse
>>> > /tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08, using
>>> > /tmp/Jetty_0_0_0_0_50070_hdfs____w2cu08_8403409681665615259
>>> > 12/06/21 14:21:54 INFO mortbay.log: Started
>>> > SelectChannelConnector@0.0.0.0:50070
>>> > 12/06/21 14:21:54 INFO namenode.NameNode: Web-server up at:
>>> > 0.0.0.0:50070
>>> > 12/06/21 14:21:54 INFO ipc.Server: IPC Server Responder: starting
>>> > 12/06/21 14:21:54 INFO ipc.Server: IPC Server listener on 54310:
>>> > starting
>>> > 12/06/21 14:21:54 INFO namenode.NameNode: NameNode up at:
>>> > localhost/127.0.0.1:54310
>>> > 12/06/21 14:21:54 INFO namenode.FSNamesystem: Starting services
>>> > required for active state
>>> >
>>> >
>>> > there are a series of process and then ir stops in the last line of
>>> > the above error snippet ..
>>> > can someone help me with this ?
>>> >
>>> > On Thu, Jun 21, 2012 at 1:00 PM, Mohammad Tariq <[EMAIL PROTECTED]>
>>> > wrote:
>>> >> Have you formatted the namenode after adding those properties??If not
>>> >> then do it. Also change the permissions of all the directories to 777.
>>> >> And use commands with fs and not dfs, like :
>>> >> $ hadoop fs - ls /
>>> >>
>>> >> Regards,
>>> >> Mohammad Tariq
>>> >>
>>> >>
>>> >> On Thu, Jun 21, 2012 at 12:53 PM, soham sardar
>>> >> <[EMAIL PROTECTED]> wrote:

Re: namenode starting error

Soham Sardar 2012-06-21, 11:54

CORE-SITE

<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
<description>The name of the default file system. A URI whose
scheme and authority determine the FileSystem implementation. The
uri's scheme determines the config property (fs.SCHEME.impl) naming
the FileSystem implementation class. The uri's authority is used to
determine the host, port, etc. for a filesystem.</description>
</property>

<property>
<name>hadoop.tmp.dir</name>
<value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/tmp</value>
</property>

hdfs site

<configuration>
<property>
  <name>dfs.replication</name>
  <value>1</value>
  <description>Default block replication.
  The actual number of replications can be specified when the file is created.
  The default is used if replication is not specified in create time.
  </description>
</property>

<property>
<name>dfs.permissions</name>
<value>false</value>
</property>

<property>
<name>dfs.name.dir</name>
<value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/name/</value>
</property>

<property>
<name>dfs.data.dir</name>
<value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/data/</value>
</property>
</configuration>
and then the Yarn site xml is also good as per required

On Thu, Jun 21, 2012 at 5:21 PM, Soham Sardar <[EMAIL PROTECTED]> wrote:
> hosts file
> soham@XPS-L501X:~$ cat /etc/hosts
> 127.0.0.1 localhost
> 127.0.1.1 XPS-L501X
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
>
> hostname file
> soham@XPS-L501X:~$ cat /etc/hostname
> XPS-L501X
>
>
>
>
> On Thu, Jun 21, 2012 at 5:15 PM, shashwat shriparv
> <[EMAIL PROTECTED]> wrote:
>> And also configuration files contents....
>>
>> On Thu, Jun 21, 2012 at 5:12 PM, shashwat shriparv
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> Dear Soham can you send the content of your /etc/hosts file and
>>> /etc/hostname file contents.... ??
>>>
>>>
>>>
>>> Regards
>>>
>>> Shashwat Shriparv
>>>
>>>
>>> On Thu, Jun 21, 2012 at 2:25 PM, soham sardar <[EMAIL PROTECTED]>
>>> wrote:
>>>>
>>>> And mohammad i formatted the namenode and then ran the command
>>>> hduser@XPS-L501X:~/cloudera/hadoop-2.0.0-cdh4.0.0$ hadoop dfs -ls
>>>>
>>>>
>>>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
>>>> Instead use the hdfs command for it.
>>>>
>>>> 12/06/21 14:23:56 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 0 time(s).
>>>> 12/06/21 14:23:57 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 1 time(s).
>>>> 12/06/21 14:23:58 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 2 time(s).
>>>> 12/06/21 14:23:59 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 3 time(s).
>>>> 12/06/21 14:24:00 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 4 time(s).
>>>> 12/06/21 14:24:01 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 5 time(s).
>>>> 12/06/21 14:24:02 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 6 time(s).
>>>> 12/06/21 14:24:03 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 7 time(s).
>>>> 12/06/21 14:24:04 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 8 time(s).
>>>> 12/06/21 14:24:05 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 9 time(s).
>>>> ls: Call From XPS-L501X/127.0.0.1 to localhost:54310 failed on
>>>> connection exception: java.net.ConnectException: Connection refused;
>>>> For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
>>>>
>>>> ??
>>>>
>>>> On Thu, Jun 21, 2012 at 2:23 PM, soham sardar <[EMAIL PROTECTED]>

Re: namenode starting error

shashwat shriparv 2012-06-21, 19:02

instead of 127.0.1.1 change it to your IP Address

Regards

∞
Shashwat Shriparv
On Thu, Jun 21, 2012 at 5:24 PM, Soham Sardar <[EMAIL PROTECTED]>wrote:

> CORE-SITE
>
> <property>
> <name>fs.default.name</name>
> <value>hdfs://localhost:54310</value>
> <description>The name of the default file system. A URI whose
> scheme and authority determine the FileSystem implementation. The
> uri's scheme determines the config property (fs.SCHEME.impl) naming
> the FileSystem implementation class. The uri's authority is used to
> determine the host, port, etc. for a filesystem.</description>
> </property>
>
> <property>
> <name>hadoop.tmp.dir</name>
> <value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/tmp</value>
> </property>
>
> hdfs site
>
> <configuration>
> <property>
> <name>dfs.replication</name>
> <value>1</value>
> <description>Default block replication.
> The actual number of replications can be specified when the file is
> created.
> The default is used if replication is not specified in create time.
> </description>
> </property>
>
> <property>
> <name>dfs.permissions</name>
> <value>false</value>
> </property>
>
> <property>
> <name>dfs.name.dir</name>
> <value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/name/</value>
> </property>
>
> <property>
> <name>dfs.data.dir</name>
> <value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/data/</value>
> </property>
> </configuration>
>
>
> and then the Yarn site xml is also good as per required
>
> On Thu, Jun 21, 2012 at 5:21 PM, Soham Sardar <[EMAIL PROTECTED]>
> wrote:
> > hosts file
> > soham@XPS-L501X:~$ cat /etc/hosts
> > 127.0.0.1 localhost
> > 127.0.1.1 XPS-L501X
> >
> > # The following lines are desirable for IPv6 capable hosts
> > ::1 ip6-localhost ip6-loopback
> > fe00::0 ip6-localnet
> > ff00::0 ip6-mcastprefix
> > ff02::1 ip6-allnodes
> > ff02::2 ip6-allrouters
> >
> > hostname file
> > soham@XPS-L501X:~$ cat /etc/hostname
> > XPS-L501X
> >
> >
> >
> >
> > On Thu, Jun 21, 2012 at 5:15 PM, shashwat shriparv
> > <[EMAIL PROTECTED]> wrote:
> >> And also configuration files contents....
> >>
> >> On Thu, Jun 21, 2012 at 5:12 PM, shashwat shriparv
> >> <[EMAIL PROTECTED]> wrote:
> >>>
> >>> Dear Soham can you send the content of your /etc/hosts file and
> >>> /etc/hostname file contents.... ??
> >>>
> >>>
> >>>
> >>> Regards
> >>>
> >>> Shashwat Shriparv
> >>>
> >>>
> >>> On Thu, Jun 21, 2012 at 2:25 PM, soham sardar <
> [EMAIL PROTECTED]>
> >>> wrote:
> >>>>
> >>>> And mohammad i formatted the namenode and then ran the command
> >>>> hduser@XPS-L501X:~/cloudera/hadoop-2.0.0-cdh4.0.0$ hadoop dfs -ls
> >>>>
> >>>>
> >>>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
> >>>> Instead use the hdfs command for it.
> >>>>
> >>>> 12/06/21 14:23:56 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 0 time(s).
> >>>> 12/06/21 14:23:57 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 1 time(s).
> >>>> 12/06/21 14:23:58 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 2 time(s).
> >>>> 12/06/21 14:23:59 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 3 time(s).
> >>>> 12/06/21 14:24:00 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 4 time(s).
> >>>> 12/06/21 14:24:01 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 5 time(s).
> >>>> 12/06/21 14:24:02 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 6 time(s).
> >>>> 12/06/21 14:24:03 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 7 time(s).
> >>>> 12/06/21 14:24:04 INFO ipc.Client: Retrying connect to server:
> >>>> localhost/127.0.0.1:54310. Already tried 8 time(s).
> >>>> 12/06/21 14:24:05 INFO ipc.Client: Retrying connect to server:

∞
Shashwat Shriparv

RE: namenode starting error

Shashwat Shriparv 2012-06-22, 07:30

Hey Soham HI.....

You setting is like this

> 127.0.0.1 localhost
> 127.0.1.1 XPS-L501X
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
>
> hostname file
> soham@XPS-L501X:~$ cat /etc/hostname
> XPS-L501X
>
Please make it like this :

> 127.0.0.1 localhost
><PUT THE SYSTEM IP ADDRESS HERE> XPS-L501X #//this you can get using ifconfig command, for example 192.168.1.22 XPS-L501X
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
>
> hostname file
> soham@XPS-L501X:~$ cat /etc/hostname
> XPS-L501X
>

And then try it should work

Regards
∞
Shashwat Shriparv

-----Original Message-----
From: Soham Sardar [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2012 5:24 PM
To: [EMAIL PROTECTED]
Subject: Re: namenode starting error

CORE-SITE

<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
<description>The name of the default file system. A URI whose
scheme and authority determine the FileSystem implementation. The
uri's scheme determines the config property (fs.SCHEME.impl) naming
the FileSystem implementation class. The uri's authority is used to
determine the host, port, etc. for a filesystem.</description>
</property>

<property>
<name>hadoop.tmp.dir</name>
<value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/tmp</value>
</property>

hdfs site

<configuration>
<property>
  <name>dfs.replication</name>
  <value>1</value>
  <description>Default block replication.
  The actual number of replications can be specified when the file is created.
  The default is used if replication is not specified in create time.
  </description>
</property>

<property>
<name>dfs.permissions</name>
<value>false</value>
</property>

<property>
<name>dfs.name.dir</name>
<value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/name/</value>
</property>

<property>
<name>dfs.data.dir</name>
<value>/home/hduser/cloudera/hadoop-2.0.0-cdh4.0.0/data/</value>
</property>
</configuration>
and then the Yarn site xml is also good as per required

On Thu, Jun 21, 2012 at 5:21 PM, Soham Sardar <[EMAIL PROTECTED]> wrote:
> hosts file
> soham@XPS-L501X:~$ cat /etc/hosts
> 127.0.0.1 localhost
> 127.0.1.1 XPS-L501X
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
>
> hostname file
> soham@XPS-L501X:~$ cat /etc/hostname
> XPS-L501X
>
>
>
>
> On Thu, Jun 21, 2012 at 5:15 PM, shashwat shriparv
> <[EMAIL PROTECTED]> wrote:
>> And also configuration files contents....
>>
>> On Thu, Jun 21, 2012 at 5:12 PM, shashwat shriparv
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> Dear Soham can you send the content of your /etc/hosts file and
>>> /etc/hostname file contents.... ??
>>>
>>>
>>>
>>> Regards
>>>
>>> Shashwat Shriparv
>>>
>>>
>>> On Thu, Jun 21, 2012 at 2:25 PM, soham sardar <[EMAIL PROTECTED]>
>>> wrote:
>>>>
>>>> And mohammad i formatted the namenode and then ran the command
>>>> hduser@XPS-L501X:~/cloudera/hadoop-2.0.0-cdh4.0.0$ hadoop dfs -ls
>>>>
>>>>
>>>> DEPRECATED: Use of this script to execute hdfs command is deprecated.
>>>> Instead use the hdfs command for it.
>>>>
>>>> 12/06/21 14:23:56 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 0 time(s).
>>>> 12/06/21 14:23:57 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 1 time(s).
>>>> 12/06/21 14:23:58 INFO ipc.Client: Retrying connect to server:
>>>> localhost/127.0.0.1:54310. Already tried 2 time(s).
>>>> 12/06/21 14:23:59 INFO ipc.Client: Retrying connect to server:

RE: namenode starting error

Siddharth Tiwari 2012-07-08, 05:32

Can you paste your namenode log here ?

*------------------------*

Cheers !!!

Siddharth Tiwari

Have a refreshing day !!!
"Every duty is holy, and devotion to duty is the highest form of worship of God.”

"Maybe other people will try to limit me but I don't limit myself"
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Date: Sat, 7 Jul 2012 21:37:16 -0400
> Subject: Re: namenode starting error
>
> Check your firewall settings, specifically if port 54310 is open. The
> other ports to look at are:
>
> 50010
> 50020
> 50030
> 50060
> 50070
> 54311
>
> On 6/20/12 5:22 AM, "soham sardar" <[EMAIL PROTECTED]> wrote:
>
> >the thing is i have updated my JAVA_HOME in both .bashrc and hadoop-env.sh
> >
> >
> >now the problem is when i try
> >jps is the output is
> >
> >6113 NodeManager
> >6799 DataNode
> >7562 Jps
> >7104 SecondaryNameNode
> >5728 ResourceManager
> >
> >and now except namenode ,all other nodes are working and when i try to
> >give
> >
> >hadoop fs -ls
> >
> >hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin$ hadoop
> >fs -ls
> >12/06/20 14:45:14 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 0 time(s).
> >12/06/20 14:45:15 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 1 time(s).
> >12/06/20 14:45:16 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 2 time(s).
> >12/06/20 14:45:17 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 3 time(s).
> >12/06/20 14:45:18 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 4 time(s).
> >12/06/20 14:45:19 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 5 time(s).
> >12/06/20 14:45:20 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 6 time(s).
> >12/06/20 14:45:21 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 7 time(s).
> >12/06/20 14:45:22 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 8 time(s).
> >12/06/20 14:45:23 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 9 time(s).
> >ls: Call From XPS-L501X/127.0.1.1 to localhost:54310 failed on
> >connection exception: java.net.ConnectException: Connection refused;
> >For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
> >
> >could u temme why this error is coming ?????????
>
>
> This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
>
>
> --------------------
>
> This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
>
>
>
>
> --------------------
>
> This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.

RE: namenode starting error

yogesh dhari 2012-07-08, 11:14

Hi,

have you formated your name node by using

hadoop namenode -format
Regards
Yogesh Kumar

> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Date: Sat, 7 Jul 2012 21:37:16 -0400
> Subject: Re: namenode starting error
>
> Check your firewall settings, specifically if port 54310 is open. The
> other ports to look at are:
>
> 50010
> 50020
> 50030
> 50060
> 50070
> 54311
>
> On 6/20/12 5:22 AM, "soham sardar" <[EMAIL PROTECTED]> wrote:
>
> >the thing is i have updated my JAVA_HOME in both .bashrc and hadoop-env.sh
> >
> >
> >now the problem is when i try
> >jps is the output is
> >
> >6113 NodeManager
> >6799 DataNode
> >7562 Jps
> >7104 SecondaryNameNode
> >5728 ResourceManager
> >
> >and now except namenode ,all other nodes are working and when i try to
> >give
> >
> >hadoop fs -ls
> >
> >hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin$ hadoop
> >fs -ls
> >12/06/20 14:45:14 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 0 time(s).
> >12/06/20 14:45:15 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 1 time(s).
> >12/06/20 14:45:16 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 2 time(s).
> >12/06/20 14:45:17 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 3 time(s).
> >12/06/20 14:45:18 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 4 time(s).
> >12/06/20 14:45:19 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 5 time(s).
> >12/06/20 14:45:20 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 6 time(s).
> >12/06/20 14:45:21 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 7 time(s).
> >12/06/20 14:45:22 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 8 time(s).
> >12/06/20 14:45:23 INFO ipc.Client: Retrying connect to server:
> >localhost/127.0.0.1:54310. Already tried 9 time(s).
> >ls: Call From XPS-L501X/127.0.1.1 to localhost:54310 failed on
> >connection exception: java.net.ConnectException: Connection refused;
> >For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
> >
> >could u temme why this error is coming ?????????
>
>
> This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
>
>
> --------------------
>
> This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
>
>
>
>
> --------------------
>
> This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.