You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@hadoop.apache.org by Xine Jar <xi...@googlemail.com> on 2009/07/06 09:34:38 UTC
problem with starting the Jobtracker and thenamenode
*Hallo, I am using Hadoop 0.18.3 on a cluster of three linux machines.
The jobtracker and the namenode cannot be started. I have copied the log
files and
the configuration file. Can someone help?*
*Jobtracker log file
*2009-07-03 17:34:09,315 INFO org.apache.hadoop.mapred.JobTracker:
STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting JobTracker
STARTUP_MSG: host = alshain/134.130.222.20
STARTUP_MSG: args = []
STARTUP_MSG: version = 0.18.3
STARTUP_MSG: build =
https://svn.apache.org/repos/asf/hadoop/core/branches/branch-0.18 -r 736250;
compiled by 'ndaley' on Thu Jan 22 23:12:08 UTC 2009
************************************************************/
2009-07-03 17:34:09,429 FATAL org.apache.hadoop.mapred.JobTracker:
java.net.BindException: Problem binding to
albali.mobnets.RWTH-Aachen.DE/134.130.222.18:9001 : Cannot assign requested
address
at org.apache.hadoop.ipc.Server.bind(Server.java:170)
at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:233)
at org.apache.hadoop.ipc.Server.<init>(Server.java:953)
at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:465)
at org.apache.hadoop.ipc.RPC.getServer(RPC.java:427)
at org.apache.hadoop.mapred.JobTracker.<init>(JobTracker.java:659)
at org.apache.hadoop.mapred.JobTracker.startTracker(JobTracker.java:131)
at org.apache.hadoop.mapred.JobTracker.main(JobTracker.java:2373)
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at org.apache.hadoop.ipc.Server.bind(Server.java:168)
... 7 more
2009-07-03 17:34:09,430 INFO org.apache.hadoop.mapred.JobTracker:
SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down JobTracker at alshain/134.130.222.20
************************************************************/
*Namenode log file*
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = alshain/134.130.222.20
STARTUP_MSG: args = []
STARTUP_MSG: version = 0.18.3
STARTUP_MSG: build =
https://svn.apache.org/repos/asf/hadoop/core/branches/branch-0.18 -r 736250;
compiled by 'ndaley' on Thu Jan 22 23:12:08 UTC 2009
************************************************************/
2009-07-03 17:33:23,246 INFO org.apache.hadoop.ipc.metrics.RpcMetrics:
Initializing RPC Metrics with hostName=NameNode, port=9000
2009-07-03 17:33:23,284 INFO org.apache.hadoop.dfs.NameNode: Namenode up at:
alshain.mobnets.rwth-aachen.de/134.130.222.20:9000
2009-07-03 17:33:23,287 INFO org.apache.hadoop.metrics.jvm.JvmMetrics:
Initializing JVM Metrics with processName=NameNode, sessionId=null
2009-07-03 17:33:23,291 INFO org.apache.hadoop.dfs.NameNodeMetrics:
Initializing NameNodeMeterics using context
object:org.apache.hadoop.metrics.spi.NullContext
2009-07-03 17:33:23,355 INFO org.apache.hadoop.fs.FSNamesystem:
fsOwner=root,root
2009-07-03 17:33:23,355 INFO org.apache.hadoop.fs.FSNamesystem:
supergroup=supergroup
2009-07-03 17:33:23,355 INFO org.apache.hadoop.fs.FSNamesystem:
isPermissionEnabled=true
2009-07-03 17:33:23,361 INFO org.apache.hadoop.dfs.FSNamesystemMetrics:
Initializing FSNamesystemMeterics using context
object:org.apache.hadoop.metrics.spi.NullContext
2009-07-03 17:33:23,362 INFO org.apache.hadoop.fs.FSNamesystem: Registered
FSNamesystemStatusMBean
2009-07-03 17:33:23,393 ERROR org.apache.hadoop.fs.FSNamesystem:
FSNamesystem initialization failed.
java.io.IOException: NameNode is not formatted.
at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:243)
at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:80)
at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:294)
at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:273)
at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:148)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:193)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:179)
at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:830)
at org.apache.hadoop.dfs.NameNode.main(NameNode.java:839)
2009-07-03 17:33:23,394 INFO org.apache.hadoop.ipc.Server: Stopping server
on 9000
2009-07-03 17:33:23,394 ERROR org.apache.hadoop.dfs.NameNode:
java.io.IOException: NameNode is not formatted.
at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:243)
at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:80)
at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:294)
at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:273)
at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:148)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:193)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:179)
at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:830)
at org.apache.hadoop.dfs.NameNode.main(NameNode.java:839)
2009-07-03 17:33:23,395 INFO org.apache.hadoop.dfs.NameNode: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at alshain/134.130.222.20
************************************************************/
*Hadoop-site.xml
*<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://134.130.222.20:9000/</value>
</property>
<property>
<name>mapred.job.tracker</name>
<value>134.130.222.18:9001</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/root/Desktop/hadoop-0.18.3/logstina</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/root/Desktop/hadoop-0.18.3/blockstina</value>
</property>
<property>
<name>mapred.system.dir</name>
<value>systemtina</value>
</property>
<property>
<name>mapred.local.dir</name>
<value>/root/Desktop/hadoop-0.18.3/tempMapReducetina</value>
</property>
</configuration>
*Thank you,
CJ*
Re: problem with starting the Jobtracker and thenamenode
Posted by "Bogdan M. Maryniuk" <bo...@gmail.com>.
On Thu, Jul 9, 2009 at 12:11 AM, Xine Jar<xi...@googlemail.com> wrote:
> Which of the books would you advice ?
google... :-)
--
Kind regards, BM
Things, that are stupid at the beginning, rarely ends up wisely.
Re: problem with starting the Jobtracker and thenamenode
Posted by Xine Jar <xi...@googlemail.com>.
Great thank you,
I can see now that all the nodes started and I shall try to run the
WordCount v1.0 example.Let' s see.
I would also like to know in which case do you advice reformatting the node?
Do I ever need to use this command again?
and concerning the book is there a possibility to know roughly the table of
content for each of the following books: ProHadoop, and Hadoop the
definitive guide? As you see I am starting basically from 0 with hadoop and
would like to reach at point where I can write my own java program/my own
search query. Which of the books would you advice ?
Thank you very much for your help
On Wed, Jul 8, 2009 at 3:25 PM, jason hadoop <ja...@gmail.com> wrote:
> 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 <xi...@googlemail.com> 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 <xi...@googlemail.com>
> > 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<xi...@googlemail.com>
> > 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 <ENTER>
> > >>
> > >> 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
>
Re: problem with starting the Jobtracker and thenamenode
Posted by jason hadoop <ja...@gmail.com>.
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 <xi...@googlemail.com> 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 <xi...@googlemail.com>
> 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<xi...@googlemail.com>
> 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 <ENTER>
> >>
> >> 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
Re: problem with starting the Jobtracker and thenamenode
Posted by Xine Jar <xi...@googlemail.com>.
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 <xi...@googlemail.com> 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<xi...@googlemail.com> 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 <ENTER>
>>
>> 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.
>>
>
>
Re: problem with starting the Jobtracker and thenamenode
Posted by Xine Jar <xi...@googlemail.com>.
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<xi...@googlemail.com> 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 <ENTER>
>
> 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.
>
Re: problem with starting the Jobtracker and thenamenode
Posted by "Bogdan M. Maryniuk" <bo...@gmail.com>.
On Mon, Jul 6, 2009 at 9:24 PM, Xine Jar<xi...@googlemail.com> 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 <ENTER>
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.
Re: problem with starting the Jobtracker and thenamenode
Posted by "Bogdan M. Maryniuk" <bo...@gmail.com>.
On Mon, Jul 6, 2009 at 4:34 PM, Xine Jar<xi...@googlemail.com> wrote:
> Caused by: java.net.BindException: Cannot assign requested address
See? That's why.
1. Make sure localhost loopback was not screwed (i.e. socket
configuration has not been removed from the IP for the system that is
showing you this error).
2. Make sure you've disabled IPv6 (either
-Djava.net.preferIPv4Stack=true or other way) and you're not suffering
from this bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6226918
3. Make sure none of instances is running on the same address — just
in case... :-)
--
Kind regards, BM
Things, that are stupid at the beginning, rarely ends up wisely.