Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of colinfreas@gmail.com designates
 209.85.210.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=NP5K5KRr1Zv/hOqALoXPo2xlkqy1x7CsDSEiCqNuWEgRxvp9hjFAYYmCMMZjxdc1WZ
         KLopWgAyGWgdqckZr0od0KESsZQvxi0M7MF1T6KiwiuflxTORs1TnjGWMENlSyg5NwHg
         cs7YQTCepJeOGxqmwdcvYitUQ9TPWSC84xUwY=
MIME-Version: 1.0
In-Reply-To: <005601cac859$f1efa760$d5cef620$@ca>
References: <003101cac84c$70c48f00$524dad00$@ca>
	 <807696.15999.qm@web63408.mail.re1.yahoo.com>
	 <005601cac859$f1efa760$d5cef620$@ca>
Date: Sat, 20 Mar 2010 15:31:14 -0400
Message-ID: <b27f65f71003201231j7a554681r4e7a6082f4fa90af@mail.gmail.com>
Subject: Re: Bad connection to FS. command aborted.
From: Colin Freas <colinfreas@gmail.com>
To: common-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001485f8612ed6310404824081f2

--001485f8612ed6310404824081f2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

any idea what the root cause was?

On Sat, Mar 20, 2010 at 2:19 PM, Katie legere <legerek@queensu.ca> wrote:

> Thank you so much - it reformatted the file system but at least now
> everything works.
> Katie
>
> -----Original Message-----
> From: Aleksandar Stupar [mailto:stupar.aleksandar@yahoo.com]
> Sent: Saturday, March 20, 2010 2:01 PM
> To: common-user@hadoop.apache.org
> Subject: Re: Bad connection to FS. command aborted.
>
> Hi,
>
> If you have a fresh install you should try formatting the name node befor=
e
> starting dfs by:
> $ bin/hadoop namenode -format
>
> P.S. you can also use -put command instead of -copyFromLocal
>
> Hope this helps,
> Aleksandar.
>
>
>
>
> ________________________________
> From: Katie legere <legerek@queensu.ca>
> To: common-user@hadoop.apache.org
> Sent: Sat, March 20, 2010 5:43:16 PM
> Subject: Bad connection to FS. command aborted.
>
>
> I=92m getting this error when I try to copy files to the
> dfs using this command:   hadoop@10:/home/ubuntu/hadoop$ bin/hadoop dfs
> -copyFromLocal /tmp/gutenberg gutenberg
>
> I tried this to see what might be the problem : hadoop@10
> :/home/ubuntu/hadoop$
> bin/hadoop namenode
>
> And got this=85
> 10/03/20 16:24:55 INFO namenode.NameNode: STARTUP_MSG:
> /************************************************************
> STARTUP_MSG: Starting NameNode
> STARTUP_MSG:   host =3D 10/0.0.0.10
> STARTUP_MSG:   args =3D []
> STARTUP_MSG:   version =3D 0.20.1
> STARTUP_MSG:   build =3D
> http://svn.apache.org/repos/asf/hadoop/common/tags/releas
> e-0.20.1-rc1 -r 810220; compiled by 'oom' on Tue Sep  1
> 20:55:56 UTC 2009
> ************************************************************/
> 10/03/20 16:25:00 INFO metrics.RpcMetrics: Initializing RPC
> Metrics with hostName=3DNameNode, port=3D54310
> 10/03/20 16:25:00 INFO namenode.NameNode: Namenode up at:
> localhost/127.0.0.1:54310
> 10/03/20 16:25:00 INFO jvm.JvmMetrics: Initializing JVM
> Metrics with processName=3DNameNode, sessionId=3Dnull
> 10/03/20 16:25:10 INFO metrics.NameNodeMetrics: Initializing
> NameNodeMeterics using context
> object:org.apache.hadoop.metrics.spi.NullContext
> 10/03/20 16:25:10 INFO namenode.FSNamesystem:
> fsOwner=3Dhadoop,hadoop
> 10/03/20 16:25:10 INFO namenode.FSNamesystem:
> supergroup=3Dsupergroup
> 10/03/20 16:25:10 INFO namenode.FSNamesystem: isPermissionEnabled=3Dtrue
> 10/03/20 16:25:15 INFO metrics.FSNamesystemMetrics:
> Initializing FSNamesystemMet
> rics using context
> object:org.apache.hadoop.metrics.spi.NullContext
> 10/03/20 16:25:15 INFO namenode.FSNamesystem: Registered
> FSNamesystemStatusMBean
> 10/03/20 16:25:20 INFO
> common.Storage: Storage directory /tmp/hadoop-hadoop/dfs/name does not
> exist.
> 10/03/20 16:25:20 ERROR namenode.FSNamesystem: FSNamesystem
> initialization failed.
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
> Directory /tmp/hadoop-hadoop/dfs/name is in an inconsistent state: storag=
e
> directory does not exist or is not
> accessible.
> at
>
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSIm=
age.java:290)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirector=
y.java:87)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesyst=
em.java:311)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.j=
ava:292)
>        at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:=
201)
>        at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:279)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.j=
ava:956)
>        at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:965)
> 10/03/20 16:25:20 INFO ipc.Server: Stopping server on 54310
> 10/03/20 16:25:20 ERROR namenode.NameNode:
> org.apache.hadoop.hdfs.server.common.
> InconsistentFSStateException: Directory
> /tmp/hadoop-hadoop/dfs/name is in an inconsistent state: storage director=
y
> does
> not exist or is not accessible.
>        at
>
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSIm=
age.java:290)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirector=
y.java:87)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesyst=
em.java:311)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.j=
ava:292)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:=
201)
>        at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:279)
>        at
>
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.j=
ava:956)
>        at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:965)
>
> 10/03/20 16:25:20 INFO namenode.NameNode: SHUTDOWN_MSG:
> /************************************************************
> SHUTDOWN_MSG: Shutting down NameNode at 10/0.0.0.10
> ************************************************************/
>
> I tried running: hadoop@10:/home/ubuntu/hadoop$
> bin/start-dfs.sh
>
> starting namenode, logging to
> /home/ubuntu/hadoop/bin/../logs/hadoop-hadoop-namenode-10.out
> localhost: starting datanode, logging to
> /home/ubuntu/hadoop/bin/../logs/hadoop-hadoop-datanode-10.out
> localhost: starting secondarynamenode, logging to
> /home/ubuntu/hadoop/bin/../logs/hadoop-hadoop-secondarynamenode-10.out
>
> Which seems good but I still
> get the same error=85
>
> Katie Legere| Senior Programmer/Analyst |
> Department of Human Resources
> 613-533-6000    x74180| Queen's University
> This e-mail is
> intended only for the recipient(s) to whom it is addressed and may contai=
n
> information that is confidential or privileged. If you are not the intend=
ed
> recipient, any disclosure or unauthorized use of this e-mail or the
> information
> contained herein or attached hereto is strictly prohibited and may be
> unlawful.
> If you have received this e-mail in error, please notify the sender
> immediately
> and delete this e-mail without reading, printing, copying or forwarding i=
t
> to
> anyone.  Thank you.
>
>
>
>
>
>

--001485f8612ed6310404824081f2--