From general-return-353-apmail-hadoop-general-archive=hadoop.apache.org@hadoop.apache.org Wed Jul 08 13:25:56 2009 Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 49214 invoked from network); 8 Jul 2009 13:25:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Jul 2009 13:25:56 -0000 Received: (qmail 77561 invoked by uid 500); 8 Jul 2009 13:26:05 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 77501 invoked by uid 500); 8 Jul 2009 13:26:05 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 77491 invoked by uid 99); 8 Jul 2009 13:26:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jul 2009 13:26:05 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jason.hadoop@gmail.com designates 209.85.212.196 as permitted sender) Received: from [209.85.212.196] (HELO mail-vw0-f196.google.com) (209.85.212.196) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jul 2009 13:25:55 +0000 Received: by vwj34 with SMTP id 34so538832vwj.5 for ; Wed, 08 Jul 2009 06:25:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=84mVGZxC2HUJDzqu8JIZc6v+CydieyTc5wr5TT3mdmU=; b=u6bwnNiJiMFRNvZErAA4196yOZZhFQEkjmhSfoOTqcsh3mSgVReCCzVbN6LC1Oe8wJ vOKcTUglwjkKwFJUMyPZ/qIV30VC5fJ82CYde+a+YYa2Klbk0dPtfC/d2Km1+d1Ee9yD a6iukvHkga3jWjp7Txn72fnpnfI368b0dTpYg= 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=OesVhUdfZ50FX5oo2nksBUJqYK5FAlg0H93KvKIrn7/QhuBlmibKkJygidh6tuyQfX ozDofzXhYSSHS8c+O9M0Tve3kImV680WFnM+5oGdxF05IDCXJTW22A3vpTSf7bHPLsIt ocSI7/PowVIbnu6KTMnzNIFlDnZV5zlrCXsio= MIME-Version: 1.0 Received: by 10.220.77.17 with SMTP id e17mr14175649vck.3.1247059532924; Wed, 08 Jul 2009 06:25:32 -0700 (PDT) In-Reply-To: <115373b00907080614k7c8cb98eq9ed056ef47b64758@mail.gmail.com> References: <115373b00907060034t170c14afmb3aef33260424a75@mail.gmail.com> <115373b00907060524p1fcb996cq2bbb86c2fe85bd5a@mail.gmail.com> <115373b00907080212n12ae70d6oc3a9c7a3c2a02fbd@mail.gmail.com> <115373b00907080614k7c8cb98eq9ed056ef47b64758@mail.gmail.com> Date: Wed, 8 Jul 2009 06:25:32 -0700 Message-ID: <314098690907080625q11360a8fhba59103f00a8aae1@mail.gmail.com> Subject: Re: problem with starting the Jobtracker and thenamenode From: jason hadoop To: general@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e64eabf4794f08046e31acdc X-Virus-Checked: Checked by ClamAV on apache.org --0016e64eabf4794f08046e31acdc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit You may need to delete the directory that you have configured for dfs storage on all of the machines in your cluster. The other issue that may happen is that the user that owns the Namenode/Datanode processes does not have write permissions on the filesystem structure to be used for dfs storage. Does the namenode format command complete successfully? On Wed, Jul 8, 2009 at 6:14 AM, Xine Jar wrote: > Thank you all for your great help, > > I finally discovered a typing error in one of my configuration files. > Therefore my jobtracker was not able to bind the address to the port. > > On the other hand I still have the Namenode which cannot be started. The > log > file shows that the namenode is not formatted although I did this. I > appreciate it if someone can point to me the folders I can delete in order > to be able to reformat the node without deleting some critical information. > please note that I have deleted once the /tmp folder and tried to reformat > but this did not help !! > > Vielen Dank, > CJ > > On Wed, Jul 8, 2009 at 11:12 AM, Xine Jar > wrote: > > > Hallo, > > I am still struggling with the same problem. In order to be sure that > IPv6 > > is not creating a problem and that the JVM is not suffering from a bug, I > > have written a TCP client/server program in Java, I let the server run on > > the same machine that was creating the binding problem and using the same > > port number. Luckily or unfortunately, the Java server could bind the > > address normally to the port, the communication between the client and > the > > server was successful, and the netstat command shows that the port is > used. > > > > I order to be sure that the problem is not a bug for hadoop I have > > installed the version 0.20.0, > > copied the same configuration and still have the same problem. > > > > *I have few questions: * > > As I have previously mentioned, the namenode cannot be started and java > > complains that the node has not been formated. The other problem is with > the > > jobtracker which is giving a binding error on the address:port. > > > > *Q1:* Is it possible that the second problem (jobtracker problem) is > > appearing because of the namenode problem? > > > > If it is a yes, how can I solve this? I have actually deleted the /tmp > > folder and reformated the node but the formatting error persists!! Do I > have > > to do something else? > > > > If it is a no, am I doing something stupid here in any of the > > configuration files?!!! > > > > *Q2: *In order to kill all the instances of the dfs and the mapred, is > it > > enough to execute the bin/stop-dfs.sh and bin/stop-mapred.sh on the > > namenode? Is it possible that the command line is showing that there is > no > > jobtracker, no namenode, ...... but in fact the port is occupied? > > > > P.S: -Whether hadoop is running or not, the netstat command is showing > > always that the port > > is free!!!!! > > - My OS is a openSuse 9* > > > > *I am trying to debug everything, because I am somehow sick of it, It is > > certainly something stupid and most probably my fault (or my > configuration > > or my way of running things) , since others managed to run hadoop on a > > cluster. I would appreciate any idea that helps to discover this the > > problem. > > > > Thank you, > > CJ > > > > > > > > On Tue, Jul 7, 2009 at 4:47 AM, Bogdan M. Maryniuk < > > bogdan.maryniuk@gmail.com> wrote: > > > >> On Mon, Jul 6, 2009 at 9:24 PM, Xine Jar > wrote: > >> > 2.How can I check that ipv6 is really disabled on my JVM? > >> > >> You've mentioned it is Linux, but how do I know what distribution of > >> Linux's zoo you use? > >> > >> On Ubuntu it is sort of like this: > >> In the file "/etc/modprobe.d/aliases" find "alias net-pf-10 ipv6", > >> remove it and add the following: > >> > >> alias net-pf-10 off > >> alias ipv6 off > >> > >> Then reboot (welcome to the Linux). > >> > >> On RedHat and derivatives it is like this: > >> echo "alias net-pf-10 off" >> /etc/modprobe.conf > >> > >> Then reboot (insert your ironic joke here). :-) > >> > >> > >> > and in which file can I insert the flag > -Djava.net.preferIPv4Stack=true? > >> It is just a JVM parameter for a networking: > >> 1. http://java.sun.com/j2se/1.4.2/docs/guide/net/properties.html > >> 2. > >> > http://java.sun.com/j2se/1.4.2/docs/guide/net/ipv6_guide/#ipv6-networking > >> > >> See $HADOOP/conf/hadoop-env.sh and look for HADOOP_OPTS that is > >> commented out by default. > >> > >> -- > >> Kind regards, BM > >> > >> Things, that are stupid at the beginning, rarely ends up wisely. > >> > > > > > -- Pro Hadoop, a book to guide you from beginner to hadoop mastery, http://www.amazon.com/dp/1430219424?tag=jewlerymall www.prohadoopbook.com a community for Hadoop Professionals --0016e64eabf4794f08046e31acdc--