You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by Mahmood Naderan <nt...@yahoo.com> on 2015/04/17 10:22:12 UTC
ipc.Client: Retrying connect to server
Hello,I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
starting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
Re: ipc.Client: Retrying connect to server
Posted by Mahmood Naderan <nt...@yahoo.com>.
Hi guys... Thanks for bringing up this thread. I forgot to post here that finally I solved the problem. Here is the tip which may be useful for someone else in the future.
You know what? When you run the format command, in the case that it need the confirmation, you have to press 'Y' (capital letter). If you, mean me!, press 'y' it doesn't format and leave an error message which causes some further problems but you ignored it (because you may think that I confirmed the format command and know everything should be fine!).
Correctly pressing 'Y' in the format command and then start-all.sh, you will see that the "ipc.client:retrying connect to server" is gone...
Regards,
Mahmood
Re: ipc.Client: Retrying connect to server
Posted by Mahmood Naderan <nt...@yahoo.com>.
Hi guys... Thanks for bringing up this thread. I forgot to post here that finally I solved the problem. Here is the tip which may be useful for someone else in the future.
You know what? When you run the format command, in the case that it need the confirmation, you have to press 'Y' (capital letter). If you, mean me!, press 'y' it doesn't format and leave an error message which causes some further problems but you ignored it (because you may think that I confirmed the format command and know everything should be fine!).
Correctly pressing 'Y' in the format command and then start-all.sh, you will see that the "ipc.client:retrying connect to server" is gone...
Regards,
Mahmood
Re: ipc.Client: Retrying connect to server
Posted by Mahmood Naderan <nt...@yahoo.com>.
Hi guys... Thanks for bringing up this thread. I forgot to post here that finally I solved the problem. Here is the tip which may be useful for someone else in the future.
You know what? When you run the format command, in the case that it need the confirmation, you have to press 'Y' (capital letter). If you, mean me!, press 'y' it doesn't format and leave an error message which causes some further problems but you ignored it (because you may think that I confirmed the format command and know everything should be fine!).
Correctly pressing 'Y' in the format command and then start-all.sh, you will see that the "ipc.client:retrying connect to server" is gone...
Regards,
Mahmood
Re: ipc.Client: Retrying connect to server
Posted by Mahmood Naderan <nt...@yahoo.com>.
Hi guys... Thanks for bringing up this thread. I forgot to post here that finally I solved the problem. Here is the tip which may be useful for someone else in the future.
You know what? When you run the format command, in the case that it need the confirmation, you have to press 'Y' (capital letter). If you, mean me!, press 'y' it doesn't format and leave an error message which causes some further problems but you ignored it (because you may think that I confirmed the format command and know everything should be fine!).
Correctly pressing 'Y' in the format command and then start-all.sh, you will see that the "ipc.client:retrying connect to server" is gone...
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Mich Talebzadeh <mi...@peridale.co.uk>.
Yes
cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
50.140.197.217 rhes564 rhes564
127.0.0.1 rhes564 localhost.localdomain localhost
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility.
From: MrAsanjar . [mailto:afsanjar@gmail.com]
Sent: 19 April 2015 18:38
To: user@hadoop.apache.org
Subject: Re: ipc.Client: Retrying connect to server
try adding "127.0.0.1 localhost" to /etc/hosts file
On Sun, Apr 19, 2015 at 12:09 PM, Mich Talebzadeh <mi...@peridale.co.uk> wrote:
Hi,
In addition, perhaps an easier approach would be a telnet to test quickly if server is started on a given port
Mine runs on port 9000 so if it works the telnet opening will be successful.
netstat -plten|grep java
tcp 0 0 0.0.0.0:10020 0.0.0.0:* LISTEN 1009 19471 6898/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:* LISTEN 1009 15758 6213/java
tcp 0 0 50.140.197.217:9000 0.0.0.0:* LISTEN 1009 15711 6113/java
tcp 0 0 0.0.0.0:50090 0.0.0.0:* LISTEN 1009 15972 6405/java
tcp 0 0 0.0.0.0:19888 0.0.0.0:* LISTEN 1009 18565 6898/java
tcp 0 0 0.0.0.0:10033 0.0.0.0:* LISTEN 1009 18343 6898/java
tcp 0 0 0.0.0.0:50070 0.0.0.0:* LISTEN 1009 15502 6113/java
tcp 0 0 0.0.0.0:10010 0.0.0.0:* LISTEN 1009 21433 7335/java
tcp 0 0 0.0.0.0:50010 0.0.0.0:* LISTEN 1009 15745 6213/java
tcp 0 0 0.0.0.0:9083 0.0.0.0:* LISTEN 1009 19481 7110/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:* LISTEN 1009 15750 6213/java
hduser@rhes564::/home/hduser/dba/bin> telnet rhes564 9000
Trying 50.140.197.217...
Connected to rhes564.
Escape character is '^]'.
HTH
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility.
From: Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
Sent: 19 April 2015 17:53
To: user@hadoop.apache.org
Subject: RE: ipc.Client: Retrying connect to server
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address) and server is not started with that port then client will retry ( and you will get following error..)..
I can able to trace that Namenode is not running From JPS report which you had posted..Please check the namenode logs ( location : /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
_____
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,
I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations
[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration
[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop
[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
starting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Mich Talebzadeh <mi...@peridale.co.uk>.
Yes
cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
50.140.197.217 rhes564 rhes564
127.0.0.1 rhes564 localhost.localdomain localhost
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility.
From: MrAsanjar . [mailto:afsanjar@gmail.com]
Sent: 19 April 2015 18:38
To: user@hadoop.apache.org
Subject: Re: ipc.Client: Retrying connect to server
try adding "127.0.0.1 localhost" to /etc/hosts file
On Sun, Apr 19, 2015 at 12:09 PM, Mich Talebzadeh <mi...@peridale.co.uk> wrote:
Hi,
In addition, perhaps an easier approach would be a telnet to test quickly if server is started on a given port
Mine runs on port 9000 so if it works the telnet opening will be successful.
netstat -plten|grep java
tcp 0 0 0.0.0.0:10020 0.0.0.0:* LISTEN 1009 19471 6898/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:* LISTEN 1009 15758 6213/java
tcp 0 0 50.140.197.217:9000 0.0.0.0:* LISTEN 1009 15711 6113/java
tcp 0 0 0.0.0.0:50090 0.0.0.0:* LISTEN 1009 15972 6405/java
tcp 0 0 0.0.0.0:19888 0.0.0.0:* LISTEN 1009 18565 6898/java
tcp 0 0 0.0.0.0:10033 0.0.0.0:* LISTEN 1009 18343 6898/java
tcp 0 0 0.0.0.0:50070 0.0.0.0:* LISTEN 1009 15502 6113/java
tcp 0 0 0.0.0.0:10010 0.0.0.0:* LISTEN 1009 21433 7335/java
tcp 0 0 0.0.0.0:50010 0.0.0.0:* LISTEN 1009 15745 6213/java
tcp 0 0 0.0.0.0:9083 0.0.0.0:* LISTEN 1009 19481 7110/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:* LISTEN 1009 15750 6213/java
hduser@rhes564::/home/hduser/dba/bin> telnet rhes564 9000
Trying 50.140.197.217...
Connected to rhes564.
Escape character is '^]'.
HTH
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility.
From: Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
Sent: 19 April 2015 17:53
To: user@hadoop.apache.org
Subject: RE: ipc.Client: Retrying connect to server
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address) and server is not started with that port then client will retry ( and you will get following error..)..
I can able to trace that Namenode is not running From JPS report which you had posted..Please check the namenode logs ( location : /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
_____
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,
I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations
[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration
[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop
[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
starting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Mich Talebzadeh <mi...@peridale.co.uk>.
Yes
cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
50.140.197.217 rhes564 rhes564
127.0.0.1 rhes564 localhost.localdomain localhost
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility.
From: MrAsanjar . [mailto:afsanjar@gmail.com]
Sent: 19 April 2015 18:38
To: user@hadoop.apache.org
Subject: Re: ipc.Client: Retrying connect to server
try adding "127.0.0.1 localhost" to /etc/hosts file
On Sun, Apr 19, 2015 at 12:09 PM, Mich Talebzadeh <mi...@peridale.co.uk> wrote:
Hi,
In addition, perhaps an easier approach would be a telnet to test quickly if server is started on a given port
Mine runs on port 9000 so if it works the telnet opening will be successful.
netstat -plten|grep java
tcp 0 0 0.0.0.0:10020 0.0.0.0:* LISTEN 1009 19471 6898/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:* LISTEN 1009 15758 6213/java
tcp 0 0 50.140.197.217:9000 0.0.0.0:* LISTEN 1009 15711 6113/java
tcp 0 0 0.0.0.0:50090 0.0.0.0:* LISTEN 1009 15972 6405/java
tcp 0 0 0.0.0.0:19888 0.0.0.0:* LISTEN 1009 18565 6898/java
tcp 0 0 0.0.0.0:10033 0.0.0.0:* LISTEN 1009 18343 6898/java
tcp 0 0 0.0.0.0:50070 0.0.0.0:* LISTEN 1009 15502 6113/java
tcp 0 0 0.0.0.0:10010 0.0.0.0:* LISTEN 1009 21433 7335/java
tcp 0 0 0.0.0.0:50010 0.0.0.0:* LISTEN 1009 15745 6213/java
tcp 0 0 0.0.0.0:9083 0.0.0.0:* LISTEN 1009 19481 7110/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:* LISTEN 1009 15750 6213/java
hduser@rhes564::/home/hduser/dba/bin> telnet rhes564 9000
Trying 50.140.197.217...
Connected to rhes564.
Escape character is '^]'.
HTH
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility.
From: Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
Sent: 19 April 2015 17:53
To: user@hadoop.apache.org
Subject: RE: ipc.Client: Retrying connect to server
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address) and server is not started with that port then client will retry ( and you will get following error..)..
I can able to trace that Namenode is not running From JPS report which you had posted..Please check the namenode logs ( location : /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
_____
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,
I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations
[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration
[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop
[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
starting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Mich Talebzadeh <mi...@peridale.co.uk>.
Yes
cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
50.140.197.217 rhes564 rhes564
127.0.0.1 rhes564 localhost.localdomain localhost
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility.
From: MrAsanjar . [mailto:afsanjar@gmail.com]
Sent: 19 April 2015 18:38
To: user@hadoop.apache.org
Subject: Re: ipc.Client: Retrying connect to server
try adding "127.0.0.1 localhost" to /etc/hosts file
On Sun, Apr 19, 2015 at 12:09 PM, Mich Talebzadeh <mi...@peridale.co.uk> wrote:
Hi,
In addition, perhaps an easier approach would be a telnet to test quickly if server is started on a given port
Mine runs on port 9000 so if it works the telnet opening will be successful.
netstat -plten|grep java
tcp 0 0 0.0.0.0:10020 0.0.0.0:* LISTEN 1009 19471 6898/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:* LISTEN 1009 15758 6213/java
tcp 0 0 50.140.197.217:9000 0.0.0.0:* LISTEN 1009 15711 6113/java
tcp 0 0 0.0.0.0:50090 0.0.0.0:* LISTEN 1009 15972 6405/java
tcp 0 0 0.0.0.0:19888 0.0.0.0:* LISTEN 1009 18565 6898/java
tcp 0 0 0.0.0.0:10033 0.0.0.0:* LISTEN 1009 18343 6898/java
tcp 0 0 0.0.0.0:50070 0.0.0.0:* LISTEN 1009 15502 6113/java
tcp 0 0 0.0.0.0:10010 0.0.0.0:* LISTEN 1009 21433 7335/java
tcp 0 0 0.0.0.0:50010 0.0.0.0:* LISTEN 1009 15745 6213/java
tcp 0 0 0.0.0.0:9083 0.0.0.0:* LISTEN 1009 19481 7110/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:* LISTEN 1009 15750 6213/java
hduser@rhes564::/home/hduser/dba/bin> telnet rhes564 9000
Trying 50.140.197.217...
Connected to rhes564.
Escape character is '^]'.
HTH
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility.
From: Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
Sent: 19 April 2015 17:53
To: user@hadoop.apache.org
Subject: RE: ipc.Client: Retrying connect to server
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address) and server is not started with that port then client will retry ( and you will get following error..)..
I can able to trace that Namenode is not running From JPS report which you had posted..Please check the namenode logs ( location : /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
_____
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,
I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations
[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration
[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop
[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
starting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
Re: ipc.Client: Retrying connect to server
Posted by "MrAsanjar ." <af...@gmail.com>.
try adding "127.0.0.1 localhost" to /etc/hosts file
On Sun, Apr 19, 2015 at 12:09 PM, Mich Talebzadeh <mi...@peridale.co.uk>
wrote:
> Hi,
>
>
>
> In addition, perhaps an easier approach would be a telnet to test quickly
> if server is started on a given port
>
>
>
> Mine runs on port 9000 so if it works the telnet opening will be
> successful.
>
>
>
> *netstat -plten|grep java*
>
>
>
> tcp 0 0 0.0.0.0:10020 0.0.0.0:*
> LISTEN 1009 19471 6898/java
>
> tcp 0 0 0.0.0.0:50020 0.0.0.0:*
> LISTEN 1009 15758 6213/java
>
> *tcp 0 0 50.140.197.217:9000
> <http://50.140.197.217:9000> 0.0.0.0:*
> LISTEN 1009 15711 6113/java*
>
> tcp 0 0 0.0.0.0:50090 0.0.0.0:*
> LISTEN 1009 15972 6405/java
>
> tcp 0 0 0.0.0.0:19888 0.0.0.0:*
> LISTEN 1009 18565 6898/java
>
> tcp 0 0 0.0.0.0:10033 0.0.0.0:*
> LISTEN 1009 18343 6898/java
>
> tcp 0 0 0.0.0.0:50070 0.0.0.0:*
> LISTEN 1009 15502 6113/java
>
> tcp 0 0 0.0.0.0:10010 0.0.0.0:*
> LISTEN 1009 21433 7335/java
>
> tcp 0 0 0.0.0.0:50010 0.0.0.0:*
> LISTEN 1009 15745 6213/java
>
> tcp 0 0 0.0.0.0:9083 0.0.0.0:*
> LISTEN 1009 19481 7110/java
>
> tcp 0 0 0.0.0.0:50075 0.0.0.0:*
> LISTEN 1009 15750 6213/java
>
>
>
> hduser@rhes564::/home/hduser/dba/bin> *telnet rhes564 9000*
>
> Trying 50.140.197.217...
>
> Connected to rhes564.
>
> Escape character is '^]'.
>
>
>
> HTH
>
>
>
> Mich Talebzadeh
>
>
>
> http://talebzadehmich.wordpress.com
>
>
>
> Author of the books* "A Practitioner’s Guide to Upgrading to Sybase** ASE
> 15", **ISBN 978-0-9563693-0-7*.
>
> co-author *"Sybase Transact SQL Guidelines Best Practices", ISBN
> 978-0-9759693-0-4*
>
> *Publications due shortly:*
>
> *Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
> Coherence Cache*
>
> *Oracle and Sybase, Concepts and Contrasts*, ISBN: 978-0-9563693-1-4, volume
> one out shortly
>
>
>
> NOTE: The information in this email is proprietary and confidential. This
> message is for the designated recipient only, if you are not the intended
> recipient, you should destroy it immediately. Any information in this
> message shall not be understood as given or endorsed by Peridale Ltd, its
> subsidiaries or their employees, unless expressly so stated. It is the
> responsibility of the recipient to ensure that this email is virus free,
> therefore neither Peridale Ltd, its subsidiaries nor their employees accept
> any responsibility.
>
>
>
> *From:* Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
> *Sent:* 19 April 2015 17:53
> *To:* user@hadoop.apache.org
> *Subject:* RE: ipc.Client: Retrying connect to server
>
>
>
> Hello Mahmood Naderan,
>
>
>
> When client is trying to connect to server with configured port(and
> address) and server is not started with that port then client will retry (
> and you will get following error..)..
>
>
>
> I can able to trace that Namenode is not running From JPS report which you
> had posted..Please check the namenode logs ( *location *:
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
>
>
> ------------------------------
>
> Date: Fri, 17 Apr 2015 08:22:12 +0000
> From: nt_mahmood@yahoo.com
> To: user@hadoop.apache.org
> Subject: ipc.Client: Retrying connect to server
>
> Hello,
>
> I have done all steps (as far as I know) to bring up the hadoop. However,
> I get the this error
>
>
>
> 15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 0 time(s).
>
>
>
> There are a lot of threads and posts regarding this error and I tried
> them. However still stuck at this error :(
>
>
>
> Can someone help me? What did I wrong?
>
>
>
>
>
>
>
>
>
> Here are the configurations:
>
>
>
> 1) Hadoop configurations
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>mapred.job.tracker</name>
> <value>localhost:54311</value>
> </property>
> <property>
> <name>mapred.child.java.opts</name>
> <value>-Xmx512m</value>
> </property>
> </configuration>
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>fs.default.name</name>
> <value>hdfs://localhost:54310</value>
> </property>
> </configuration>
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>dfs.replication</name>
> <value>1</value>
> </property>
> <property>
> <name>hadoop.tmp.dir</name>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
> </property>
> <property>
> <name>dfs.name.dir</name>
>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
> </property>
> <property>
> <name>dfs.data.dir</name>
>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
> </property>
> </configuration>
>
>
>
>
>
>
>
>
>
>
>
> 2) Network configuration
>
> [root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
> # Firewall configuration written by system-config-firewall
> # Manual customization of this file is not recommended.
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> -A INPUT -p icmp -j ACCEPT
> -A INPUT -i lo -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
> -A INPUT -j REJECT --reject-with icmp-host-prohibited
> -A FORWARD -j REJECT --reject-with icmp-host-prohibited
> COMMIT
>
>
>
> [root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
> iptables: Flushing firewall rules: [ OK ]
> iptables: Setting chains to policy ACCEPT: filter [ OK ]
> iptables: Unloading modules: [ OK ]
> iptables: Applying firewall rules: [ OK ]
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
>
> [mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
> tcp 0 0 ::ffff:127.0.0.1:54311
> :::* LISTEN
> tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639
> ESTABLISHED
> tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311
> ESTABLISHED
>
>
>
>
>
>
>
>
>
>
>
>
>
> 3) Starting Hadoop
>
> [mahmood@tiger hadoop-1.0.2]$ stop-all.sh
> Warning: $HADOOP_HOME is deprecated.
>
> stopping jobtracker
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: stopping tasktracker
> no namenode to stop
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: no datanode to stop
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: stopping secondarynamenode
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ start-all.sh
> Warning: $HADOOP_HOME is deprecated.
>
> starting namenode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting datanode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting secondarynamenode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
> starting jobtracker, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting tasktracker, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ jps
> 21712 JobTracker
> 21882 TaskTracker
> 21580 SecondaryNameNode
> 21989 Jps
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
> Warning: $HADOOP_HOME is deprecated.
> 15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 0 time(s).
> 15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 1 time(s).
>
>
>
> Regards,
> Mahmood
>
Re: ipc.Client: Retrying connect to server
Posted by "MrAsanjar ." <af...@gmail.com>.
try adding "127.0.0.1 localhost" to /etc/hosts file
On Sun, Apr 19, 2015 at 12:09 PM, Mich Talebzadeh <mi...@peridale.co.uk>
wrote:
> Hi,
>
>
>
> In addition, perhaps an easier approach would be a telnet to test quickly
> if server is started on a given port
>
>
>
> Mine runs on port 9000 so if it works the telnet opening will be
> successful.
>
>
>
> *netstat -plten|grep java*
>
>
>
> tcp 0 0 0.0.0.0:10020 0.0.0.0:*
> LISTEN 1009 19471 6898/java
>
> tcp 0 0 0.0.0.0:50020 0.0.0.0:*
> LISTEN 1009 15758 6213/java
>
> *tcp 0 0 50.140.197.217:9000
> <http://50.140.197.217:9000> 0.0.0.0:*
> LISTEN 1009 15711 6113/java*
>
> tcp 0 0 0.0.0.0:50090 0.0.0.0:*
> LISTEN 1009 15972 6405/java
>
> tcp 0 0 0.0.0.0:19888 0.0.0.0:*
> LISTEN 1009 18565 6898/java
>
> tcp 0 0 0.0.0.0:10033 0.0.0.0:*
> LISTEN 1009 18343 6898/java
>
> tcp 0 0 0.0.0.0:50070 0.0.0.0:*
> LISTEN 1009 15502 6113/java
>
> tcp 0 0 0.0.0.0:10010 0.0.0.0:*
> LISTEN 1009 21433 7335/java
>
> tcp 0 0 0.0.0.0:50010 0.0.0.0:*
> LISTEN 1009 15745 6213/java
>
> tcp 0 0 0.0.0.0:9083 0.0.0.0:*
> LISTEN 1009 19481 7110/java
>
> tcp 0 0 0.0.0.0:50075 0.0.0.0:*
> LISTEN 1009 15750 6213/java
>
>
>
> hduser@rhes564::/home/hduser/dba/bin> *telnet rhes564 9000*
>
> Trying 50.140.197.217...
>
> Connected to rhes564.
>
> Escape character is '^]'.
>
>
>
> HTH
>
>
>
> Mich Talebzadeh
>
>
>
> http://talebzadehmich.wordpress.com
>
>
>
> Author of the books* "A Practitioner’s Guide to Upgrading to Sybase** ASE
> 15", **ISBN 978-0-9563693-0-7*.
>
> co-author *"Sybase Transact SQL Guidelines Best Practices", ISBN
> 978-0-9759693-0-4*
>
> *Publications due shortly:*
>
> *Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
> Coherence Cache*
>
> *Oracle and Sybase, Concepts and Contrasts*, ISBN: 978-0-9563693-1-4, volume
> one out shortly
>
>
>
> NOTE: The information in this email is proprietary and confidential. This
> message is for the designated recipient only, if you are not the intended
> recipient, you should destroy it immediately. Any information in this
> message shall not be understood as given or endorsed by Peridale Ltd, its
> subsidiaries or their employees, unless expressly so stated. It is the
> responsibility of the recipient to ensure that this email is virus free,
> therefore neither Peridale Ltd, its subsidiaries nor their employees accept
> any responsibility.
>
>
>
> *From:* Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
> *Sent:* 19 April 2015 17:53
> *To:* user@hadoop.apache.org
> *Subject:* RE: ipc.Client: Retrying connect to server
>
>
>
> Hello Mahmood Naderan,
>
>
>
> When client is trying to connect to server with configured port(and
> address) and server is not started with that port then client will retry (
> and you will get following error..)..
>
>
>
> I can able to trace that Namenode is not running From JPS report which you
> had posted..Please check the namenode logs ( *location *:
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
>
>
> ------------------------------
>
> Date: Fri, 17 Apr 2015 08:22:12 +0000
> From: nt_mahmood@yahoo.com
> To: user@hadoop.apache.org
> Subject: ipc.Client: Retrying connect to server
>
> Hello,
>
> I have done all steps (as far as I know) to bring up the hadoop. However,
> I get the this error
>
>
>
> 15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 0 time(s).
>
>
>
> There are a lot of threads and posts regarding this error and I tried
> them. However still stuck at this error :(
>
>
>
> Can someone help me? What did I wrong?
>
>
>
>
>
>
>
>
>
> Here are the configurations:
>
>
>
> 1) Hadoop configurations
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>mapred.job.tracker</name>
> <value>localhost:54311</value>
> </property>
> <property>
> <name>mapred.child.java.opts</name>
> <value>-Xmx512m</value>
> </property>
> </configuration>
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>fs.default.name</name>
> <value>hdfs://localhost:54310</value>
> </property>
> </configuration>
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>dfs.replication</name>
> <value>1</value>
> </property>
> <property>
> <name>hadoop.tmp.dir</name>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
> </property>
> <property>
> <name>dfs.name.dir</name>
>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
> </property>
> <property>
> <name>dfs.data.dir</name>
>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
> </property>
> </configuration>
>
>
>
>
>
>
>
>
>
>
>
> 2) Network configuration
>
> [root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
> # Firewall configuration written by system-config-firewall
> # Manual customization of this file is not recommended.
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> -A INPUT -p icmp -j ACCEPT
> -A INPUT -i lo -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
> -A INPUT -j REJECT --reject-with icmp-host-prohibited
> -A FORWARD -j REJECT --reject-with icmp-host-prohibited
> COMMIT
>
>
>
> [root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
> iptables: Flushing firewall rules: [ OK ]
> iptables: Setting chains to policy ACCEPT: filter [ OK ]
> iptables: Unloading modules: [ OK ]
> iptables: Applying firewall rules: [ OK ]
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
>
> [mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
> tcp 0 0 ::ffff:127.0.0.1:54311
> :::* LISTEN
> tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639
> ESTABLISHED
> tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311
> ESTABLISHED
>
>
>
>
>
>
>
>
>
>
>
>
>
> 3) Starting Hadoop
>
> [mahmood@tiger hadoop-1.0.2]$ stop-all.sh
> Warning: $HADOOP_HOME is deprecated.
>
> stopping jobtracker
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: stopping tasktracker
> no namenode to stop
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: no datanode to stop
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: stopping secondarynamenode
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ start-all.sh
> Warning: $HADOOP_HOME is deprecated.
>
> starting namenode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting datanode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting secondarynamenode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
> starting jobtracker, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting tasktracker, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ jps
> 21712 JobTracker
> 21882 TaskTracker
> 21580 SecondaryNameNode
> 21989 Jps
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
> Warning: $HADOOP_HOME is deprecated.
> 15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 0 time(s).
> 15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 1 time(s).
>
>
>
> Regards,
> Mahmood
>
Re: ipc.Client: Retrying connect to server
Posted by "MrAsanjar ." <af...@gmail.com>.
try adding "127.0.0.1 localhost" to /etc/hosts file
On Sun, Apr 19, 2015 at 12:09 PM, Mich Talebzadeh <mi...@peridale.co.uk>
wrote:
> Hi,
>
>
>
> In addition, perhaps an easier approach would be a telnet to test quickly
> if server is started on a given port
>
>
>
> Mine runs on port 9000 so if it works the telnet opening will be
> successful.
>
>
>
> *netstat -plten|grep java*
>
>
>
> tcp 0 0 0.0.0.0:10020 0.0.0.0:*
> LISTEN 1009 19471 6898/java
>
> tcp 0 0 0.0.0.0:50020 0.0.0.0:*
> LISTEN 1009 15758 6213/java
>
> *tcp 0 0 50.140.197.217:9000
> <http://50.140.197.217:9000> 0.0.0.0:*
> LISTEN 1009 15711 6113/java*
>
> tcp 0 0 0.0.0.0:50090 0.0.0.0:*
> LISTEN 1009 15972 6405/java
>
> tcp 0 0 0.0.0.0:19888 0.0.0.0:*
> LISTEN 1009 18565 6898/java
>
> tcp 0 0 0.0.0.0:10033 0.0.0.0:*
> LISTEN 1009 18343 6898/java
>
> tcp 0 0 0.0.0.0:50070 0.0.0.0:*
> LISTEN 1009 15502 6113/java
>
> tcp 0 0 0.0.0.0:10010 0.0.0.0:*
> LISTEN 1009 21433 7335/java
>
> tcp 0 0 0.0.0.0:50010 0.0.0.0:*
> LISTEN 1009 15745 6213/java
>
> tcp 0 0 0.0.0.0:9083 0.0.0.0:*
> LISTEN 1009 19481 7110/java
>
> tcp 0 0 0.0.0.0:50075 0.0.0.0:*
> LISTEN 1009 15750 6213/java
>
>
>
> hduser@rhes564::/home/hduser/dba/bin> *telnet rhes564 9000*
>
> Trying 50.140.197.217...
>
> Connected to rhes564.
>
> Escape character is '^]'.
>
>
>
> HTH
>
>
>
> Mich Talebzadeh
>
>
>
> http://talebzadehmich.wordpress.com
>
>
>
> Author of the books* "A Practitioner’s Guide to Upgrading to Sybase** ASE
> 15", **ISBN 978-0-9563693-0-7*.
>
> co-author *"Sybase Transact SQL Guidelines Best Practices", ISBN
> 978-0-9759693-0-4*
>
> *Publications due shortly:*
>
> *Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
> Coherence Cache*
>
> *Oracle and Sybase, Concepts and Contrasts*, ISBN: 978-0-9563693-1-4, volume
> one out shortly
>
>
>
> NOTE: The information in this email is proprietary and confidential. This
> message is for the designated recipient only, if you are not the intended
> recipient, you should destroy it immediately. Any information in this
> message shall not be understood as given or endorsed by Peridale Ltd, its
> subsidiaries or their employees, unless expressly so stated. It is the
> responsibility of the recipient to ensure that this email is virus free,
> therefore neither Peridale Ltd, its subsidiaries nor their employees accept
> any responsibility.
>
>
>
> *From:* Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
> *Sent:* 19 April 2015 17:53
> *To:* user@hadoop.apache.org
> *Subject:* RE: ipc.Client: Retrying connect to server
>
>
>
> Hello Mahmood Naderan,
>
>
>
> When client is trying to connect to server with configured port(and
> address) and server is not started with that port then client will retry (
> and you will get following error..)..
>
>
>
> I can able to trace that Namenode is not running From JPS report which you
> had posted..Please check the namenode logs ( *location *:
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
>
>
> ------------------------------
>
> Date: Fri, 17 Apr 2015 08:22:12 +0000
> From: nt_mahmood@yahoo.com
> To: user@hadoop.apache.org
> Subject: ipc.Client: Retrying connect to server
>
> Hello,
>
> I have done all steps (as far as I know) to bring up the hadoop. However,
> I get the this error
>
>
>
> 15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 0 time(s).
>
>
>
> There are a lot of threads and posts regarding this error and I tried
> them. However still stuck at this error :(
>
>
>
> Can someone help me? What did I wrong?
>
>
>
>
>
>
>
>
>
> Here are the configurations:
>
>
>
> 1) Hadoop configurations
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>mapred.job.tracker</name>
> <value>localhost:54311</value>
> </property>
> <property>
> <name>mapred.child.java.opts</name>
> <value>-Xmx512m</value>
> </property>
> </configuration>
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>fs.default.name</name>
> <value>hdfs://localhost:54310</value>
> </property>
> </configuration>
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>dfs.replication</name>
> <value>1</value>
> </property>
> <property>
> <name>hadoop.tmp.dir</name>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
> </property>
> <property>
> <name>dfs.name.dir</name>
>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
> </property>
> <property>
> <name>dfs.data.dir</name>
>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
> </property>
> </configuration>
>
>
>
>
>
>
>
>
>
>
>
> 2) Network configuration
>
> [root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
> # Firewall configuration written by system-config-firewall
> # Manual customization of this file is not recommended.
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> -A INPUT -p icmp -j ACCEPT
> -A INPUT -i lo -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
> -A INPUT -j REJECT --reject-with icmp-host-prohibited
> -A FORWARD -j REJECT --reject-with icmp-host-prohibited
> COMMIT
>
>
>
> [root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
> iptables: Flushing firewall rules: [ OK ]
> iptables: Setting chains to policy ACCEPT: filter [ OK ]
> iptables: Unloading modules: [ OK ]
> iptables: Applying firewall rules: [ OK ]
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
>
> [mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
> tcp 0 0 ::ffff:127.0.0.1:54311
> :::* LISTEN
> tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639
> ESTABLISHED
> tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311
> ESTABLISHED
>
>
>
>
>
>
>
>
>
>
>
>
>
> 3) Starting Hadoop
>
> [mahmood@tiger hadoop-1.0.2]$ stop-all.sh
> Warning: $HADOOP_HOME is deprecated.
>
> stopping jobtracker
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: stopping tasktracker
> no namenode to stop
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: no datanode to stop
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: stopping secondarynamenode
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ start-all.sh
> Warning: $HADOOP_HOME is deprecated.
>
> starting namenode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting datanode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting secondarynamenode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
> starting jobtracker, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting tasktracker, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ jps
> 21712 JobTracker
> 21882 TaskTracker
> 21580 SecondaryNameNode
> 21989 Jps
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
> Warning: $HADOOP_HOME is deprecated.
> 15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 0 time(s).
> 15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 1 time(s).
>
>
>
> Regards,
> Mahmood
>
Re: ipc.Client: Retrying connect to server
Posted by "MrAsanjar ." <af...@gmail.com>.
try adding "127.0.0.1 localhost" to /etc/hosts file
On Sun, Apr 19, 2015 at 12:09 PM, Mich Talebzadeh <mi...@peridale.co.uk>
wrote:
> Hi,
>
>
>
> In addition, perhaps an easier approach would be a telnet to test quickly
> if server is started on a given port
>
>
>
> Mine runs on port 9000 so if it works the telnet opening will be
> successful.
>
>
>
> *netstat -plten|grep java*
>
>
>
> tcp 0 0 0.0.0.0:10020 0.0.0.0:*
> LISTEN 1009 19471 6898/java
>
> tcp 0 0 0.0.0.0:50020 0.0.0.0:*
> LISTEN 1009 15758 6213/java
>
> *tcp 0 0 50.140.197.217:9000
> <http://50.140.197.217:9000> 0.0.0.0:*
> LISTEN 1009 15711 6113/java*
>
> tcp 0 0 0.0.0.0:50090 0.0.0.0:*
> LISTEN 1009 15972 6405/java
>
> tcp 0 0 0.0.0.0:19888 0.0.0.0:*
> LISTEN 1009 18565 6898/java
>
> tcp 0 0 0.0.0.0:10033 0.0.0.0:*
> LISTEN 1009 18343 6898/java
>
> tcp 0 0 0.0.0.0:50070 0.0.0.0:*
> LISTEN 1009 15502 6113/java
>
> tcp 0 0 0.0.0.0:10010 0.0.0.0:*
> LISTEN 1009 21433 7335/java
>
> tcp 0 0 0.0.0.0:50010 0.0.0.0:*
> LISTEN 1009 15745 6213/java
>
> tcp 0 0 0.0.0.0:9083 0.0.0.0:*
> LISTEN 1009 19481 7110/java
>
> tcp 0 0 0.0.0.0:50075 0.0.0.0:*
> LISTEN 1009 15750 6213/java
>
>
>
> hduser@rhes564::/home/hduser/dba/bin> *telnet rhes564 9000*
>
> Trying 50.140.197.217...
>
> Connected to rhes564.
>
> Escape character is '^]'.
>
>
>
> HTH
>
>
>
> Mich Talebzadeh
>
>
>
> http://talebzadehmich.wordpress.com
>
>
>
> Author of the books* "A Practitioner’s Guide to Upgrading to Sybase** ASE
> 15", **ISBN 978-0-9563693-0-7*.
>
> co-author *"Sybase Transact SQL Guidelines Best Practices", ISBN
> 978-0-9759693-0-4*
>
> *Publications due shortly:*
>
> *Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
> Coherence Cache*
>
> *Oracle and Sybase, Concepts and Contrasts*, ISBN: 978-0-9563693-1-4, volume
> one out shortly
>
>
>
> NOTE: The information in this email is proprietary and confidential. This
> message is for the designated recipient only, if you are not the intended
> recipient, you should destroy it immediately. Any information in this
> message shall not be understood as given or endorsed by Peridale Ltd, its
> subsidiaries or their employees, unless expressly so stated. It is the
> responsibility of the recipient to ensure that this email is virus free,
> therefore neither Peridale Ltd, its subsidiaries nor their employees accept
> any responsibility.
>
>
>
> *From:* Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
> *Sent:* 19 April 2015 17:53
> *To:* user@hadoop.apache.org
> *Subject:* RE: ipc.Client: Retrying connect to server
>
>
>
> Hello Mahmood Naderan,
>
>
>
> When client is trying to connect to server with configured port(and
> address) and server is not started with that port then client will retry (
> and you will get following error..)..
>
>
>
> I can able to trace that Namenode is not running From JPS report which you
> had posted..Please check the namenode logs ( *location *:
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
>
>
> ------------------------------
>
> Date: Fri, 17 Apr 2015 08:22:12 +0000
> From: nt_mahmood@yahoo.com
> To: user@hadoop.apache.org
> Subject: ipc.Client: Retrying connect to server
>
> Hello,
>
> I have done all steps (as far as I know) to bring up the hadoop. However,
> I get the this error
>
>
>
> 15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 0 time(s).
>
>
>
> There are a lot of threads and posts regarding this error and I tried
> them. However still stuck at this error :(
>
>
>
> Can someone help me? What did I wrong?
>
>
>
>
>
>
>
>
>
> Here are the configurations:
>
>
>
> 1) Hadoop configurations
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>mapred.job.tracker</name>
> <value>localhost:54311</value>
> </property>
> <property>
> <name>mapred.child.java.opts</name>
> <value>-Xmx512m</value>
> </property>
> </configuration>
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>fs.default.name</name>
> <value>hdfs://localhost:54310</value>
> </property>
> </configuration>
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <!-- Put site-specific property overrides in this file. -->
> <configuration>
> <property>
> <name>dfs.replication</name>
> <value>1</value>
> </property>
> <property>
> <name>hadoop.tmp.dir</name>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
> </property>
> <property>
> <name>dfs.name.dir</name>
>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
> </property>
> <property>
> <name>dfs.data.dir</name>
>
> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
> </property>
> </configuration>
>
>
>
>
>
>
>
>
>
>
>
> 2) Network configuration
>
> [root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
> # Firewall configuration written by system-config-firewall
> # Manual customization of this file is not recommended.
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> -A INPUT -p icmp -j ACCEPT
> -A INPUT -i lo -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
> -A INPUT -j REJECT --reject-with icmp-host-prohibited
> -A FORWARD -j REJECT --reject-with icmp-host-prohibited
> COMMIT
>
>
>
> [root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
> iptables: Flushing firewall rules: [ OK ]
> iptables: Setting chains to policy ACCEPT: filter [ OK ]
> iptables: Unloading modules: [ OK ]
> iptables: Applying firewall rules: [ OK ]
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
>
> [mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
> tcp 0 0 ::ffff:127.0.0.1:54311
> :::* LISTEN
> tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639
> ESTABLISHED
> tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311
> ESTABLISHED
>
>
>
>
>
>
>
>
>
>
>
>
>
> 3) Starting Hadoop
>
> [mahmood@tiger hadoop-1.0.2]$ stop-all.sh
> Warning: $HADOOP_HOME is deprecated.
>
> stopping jobtracker
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: stopping tasktracker
> no namenode to stop
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: no datanode to stop
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: stopping secondarynamenode
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ start-all.sh
> Warning: $HADOOP_HOME is deprecated.
>
> starting namenode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting datanode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting secondarynamenode, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.out
> starting jobtracker, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.out
> localhost: Warning: $HADOOP_HOME is deprecated.
> localhost:
> localhost: starting tasktracker, logging to
> /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ jps
> 21712 JobTracker
> 21882 TaskTracker
> 21580 SecondaryNameNode
> 21989 Jps
>
>
>
> [mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
> Warning: $HADOOP_HOME is deprecated.
> 15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 0 time(s).
> 15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/
> 127.0.0.1:54310. Already tried 1 time(s).
>
>
>
> Regards,
> Mahmood
>
RE: ipc.Client: Retrying connect to server
Posted by Mich Talebzadeh <mi...@peridale.co.uk>.
Hi,
In addition, perhaps an easier approach would be a telnet to test quickly if
server is started on a given port
Mine runs on port 9000 so if it works the telnet opening will be successful.
netstat -plten|grep java
tcp 0 0 0.0.0.0:10020 0.0.0.0:*
LISTEN 1009 19471 6898/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:*
LISTEN 1009 15758 6213/java
tcp 0 0 50.140.197.217:9000 0.0.0.0:*
LISTEN 1009 15711 6113/java
tcp 0 0 0.0.0.0:50090 0.0.0.0:*
LISTEN 1009 15972 6405/java
tcp 0 0 0.0.0.0:19888 0.0.0.0:*
LISTEN 1009 18565 6898/java
tcp 0 0 0.0.0.0:10033 0.0.0.0:*
LISTEN 1009 18343 6898/java
tcp 0 0 0.0.0.0:50070 0.0.0.0:*
LISTEN 1009 15502 6113/java
tcp 0 0 0.0.0.0:10010 0.0.0.0:*
LISTEN 1009 21433 7335/java
tcp 0 0 0.0.0.0:50010 0.0.0.0:*
LISTEN 1009 15745 6213/java
tcp 0 0 0.0.0.0:9083 0.0.0.0:*
LISTEN 1009 19481 7110/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:*
LISTEN 1009 15750 6213/java
hduser@rhes564::/home/hduser/dba/bin> telnet rhes564 9000
Trying 50.140.197.217...
Connected to rhes564.
Escape character is '^]'.
HTH
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner's Guide to Upgrading to Sybase ASE 15",
ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN
978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume
one out shortly
NOTE: The information in this email is proprietary and confidential. This
message is for the designated recipient only, if you are not the intended
recipient, you should destroy it immediately. Any information in this
message shall not be understood as given or endorsed by Peridale Ltd, its
subsidiaries or their employees, unless expressly so stated. It is the
responsibility of the recipient to ensure that this email is virus free,
therefore neither Peridale Ltd, its subsidiaries nor their employees accept
any responsibility.
From: Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
Sent: 19 April 2015 17:53
To: user@hadoop.apache.org
Subject: RE: ipc.Client: Retrying connect to server
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address)
and server is not started with that port then client will retry ( and you
will get following error..)..
I can able to trace that Namenode is not running From JPS report which you
had posted..Please check the namenode logs ( location :
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-namenode-tiger.out/log)
_____
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,
I have done all steps (as far as I know) to bring up the hadoop. However, I
get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them.
However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations
[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration
[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::*
LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311
ESTABLISHED
3) Starting Hadoop
[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-secondarynamenode-tiger.out
starting jobtracker, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Mich Talebzadeh <mi...@peridale.co.uk>.
Hi,
In addition, perhaps an easier approach would be a telnet to test quickly if
server is started on a given port
Mine runs on port 9000 so if it works the telnet opening will be successful.
netstat -plten|grep java
tcp 0 0 0.0.0.0:10020 0.0.0.0:*
LISTEN 1009 19471 6898/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:*
LISTEN 1009 15758 6213/java
tcp 0 0 50.140.197.217:9000 0.0.0.0:*
LISTEN 1009 15711 6113/java
tcp 0 0 0.0.0.0:50090 0.0.0.0:*
LISTEN 1009 15972 6405/java
tcp 0 0 0.0.0.0:19888 0.0.0.0:*
LISTEN 1009 18565 6898/java
tcp 0 0 0.0.0.0:10033 0.0.0.0:*
LISTEN 1009 18343 6898/java
tcp 0 0 0.0.0.0:50070 0.0.0.0:*
LISTEN 1009 15502 6113/java
tcp 0 0 0.0.0.0:10010 0.0.0.0:*
LISTEN 1009 21433 7335/java
tcp 0 0 0.0.0.0:50010 0.0.0.0:*
LISTEN 1009 15745 6213/java
tcp 0 0 0.0.0.0:9083 0.0.0.0:*
LISTEN 1009 19481 7110/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:*
LISTEN 1009 15750 6213/java
hduser@rhes564::/home/hduser/dba/bin> telnet rhes564 9000
Trying 50.140.197.217...
Connected to rhes564.
Escape character is '^]'.
HTH
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner's Guide to Upgrading to Sybase ASE 15",
ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN
978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume
one out shortly
NOTE: The information in this email is proprietary and confidential. This
message is for the designated recipient only, if you are not the intended
recipient, you should destroy it immediately. Any information in this
message shall not be understood as given or endorsed by Peridale Ltd, its
subsidiaries or their employees, unless expressly so stated. It is the
responsibility of the recipient to ensure that this email is virus free,
therefore neither Peridale Ltd, its subsidiaries nor their employees accept
any responsibility.
From: Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
Sent: 19 April 2015 17:53
To: user@hadoop.apache.org
Subject: RE: ipc.Client: Retrying connect to server
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address)
and server is not started with that port then client will retry ( and you
will get following error..)..
I can able to trace that Namenode is not running From JPS report which you
had posted..Please check the namenode logs ( location :
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-namenode-tiger.out/log)
_____
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,
I have done all steps (as far as I know) to bring up the hadoop. However, I
get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them.
However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations
[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration
[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::*
LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311
ESTABLISHED
3) Starting Hadoop
[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-secondarynamenode-tiger.out
starting jobtracker, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Mich Talebzadeh <mi...@peridale.co.uk>.
Hi,
In addition, perhaps an easier approach would be a telnet to test quickly if
server is started on a given port
Mine runs on port 9000 so if it works the telnet opening will be successful.
netstat -plten|grep java
tcp 0 0 0.0.0.0:10020 0.0.0.0:*
LISTEN 1009 19471 6898/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:*
LISTEN 1009 15758 6213/java
tcp 0 0 50.140.197.217:9000 0.0.0.0:*
LISTEN 1009 15711 6113/java
tcp 0 0 0.0.0.0:50090 0.0.0.0:*
LISTEN 1009 15972 6405/java
tcp 0 0 0.0.0.0:19888 0.0.0.0:*
LISTEN 1009 18565 6898/java
tcp 0 0 0.0.0.0:10033 0.0.0.0:*
LISTEN 1009 18343 6898/java
tcp 0 0 0.0.0.0:50070 0.0.0.0:*
LISTEN 1009 15502 6113/java
tcp 0 0 0.0.0.0:10010 0.0.0.0:*
LISTEN 1009 21433 7335/java
tcp 0 0 0.0.0.0:50010 0.0.0.0:*
LISTEN 1009 15745 6213/java
tcp 0 0 0.0.0.0:9083 0.0.0.0:*
LISTEN 1009 19481 7110/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:*
LISTEN 1009 15750 6213/java
hduser@rhes564::/home/hduser/dba/bin> telnet rhes564 9000
Trying 50.140.197.217...
Connected to rhes564.
Escape character is '^]'.
HTH
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner's Guide to Upgrading to Sybase ASE 15",
ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN
978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume
one out shortly
NOTE: The information in this email is proprietary and confidential. This
message is for the designated recipient only, if you are not the intended
recipient, you should destroy it immediately. Any information in this
message shall not be understood as given or endorsed by Peridale Ltd, its
subsidiaries or their employees, unless expressly so stated. It is the
responsibility of the recipient to ensure that this email is virus free,
therefore neither Peridale Ltd, its subsidiaries nor their employees accept
any responsibility.
From: Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
Sent: 19 April 2015 17:53
To: user@hadoop.apache.org
Subject: RE: ipc.Client: Retrying connect to server
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address)
and server is not started with that port then client will retry ( and you
will get following error..)..
I can able to trace that Namenode is not running From JPS report which you
had posted..Please check the namenode logs ( location :
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-namenode-tiger.out/log)
_____
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,
I have done all steps (as far as I know) to bring up the hadoop. However, I
get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them.
However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations
[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration
[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::*
LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311
ESTABLISHED
3) Starting Hadoop
[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-secondarynamenode-tiger.out
starting jobtracker, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Mich Talebzadeh <mi...@peridale.co.uk>.
Hi,
In addition, perhaps an easier approach would be a telnet to test quickly if
server is started on a given port
Mine runs on port 9000 so if it works the telnet opening will be successful.
netstat -plten|grep java
tcp 0 0 0.0.0.0:10020 0.0.0.0:*
LISTEN 1009 19471 6898/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:*
LISTEN 1009 15758 6213/java
tcp 0 0 50.140.197.217:9000 0.0.0.0:*
LISTEN 1009 15711 6113/java
tcp 0 0 0.0.0.0:50090 0.0.0.0:*
LISTEN 1009 15972 6405/java
tcp 0 0 0.0.0.0:19888 0.0.0.0:*
LISTEN 1009 18565 6898/java
tcp 0 0 0.0.0.0:10033 0.0.0.0:*
LISTEN 1009 18343 6898/java
tcp 0 0 0.0.0.0:50070 0.0.0.0:*
LISTEN 1009 15502 6113/java
tcp 0 0 0.0.0.0:10010 0.0.0.0:*
LISTEN 1009 21433 7335/java
tcp 0 0 0.0.0.0:50010 0.0.0.0:*
LISTEN 1009 15745 6213/java
tcp 0 0 0.0.0.0:9083 0.0.0.0:*
LISTEN 1009 19481 7110/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:*
LISTEN 1009 15750 6213/java
hduser@rhes564::/home/hduser/dba/bin> telnet rhes564 9000
Trying 50.140.197.217...
Connected to rhes564.
Escape character is '^]'.
HTH
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner's Guide to Upgrading to Sybase ASE 15",
ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN
978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume
one out shortly
NOTE: The information in this email is proprietary and confidential. This
message is for the designated recipient only, if you are not the intended
recipient, you should destroy it immediately. Any information in this
message shall not be understood as given or endorsed by Peridale Ltd, its
subsidiaries or their employees, unless expressly so stated. It is the
responsibility of the recipient to ensure that this email is virus free,
therefore neither Peridale Ltd, its subsidiaries nor their employees accept
any responsibility.
From: Brahma Reddy Battula [mailto:brahmareddy.battula@hotmail.com]
Sent: 19 April 2015 17:53
To: user@hadoop.apache.org
Subject: RE: ipc.Client: Retrying connect to server
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address)
and server is not started with that port then client will retry ( and you
will get following error..)..
I can able to trace that Namenode is not running From JPS report which you
had posted..Please check the namenode logs ( location :
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-namenode-tiger.out/log)
_____
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,
I have done all steps (as far as I know) to bring up the hadoop. However, I
get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them.
However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations
[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:54311</value>
</property>
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx512m</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!-- Put site-specific property overrides in this file. -->
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value>
</property>
<property>
<name>dfs.name.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value>
</property>
<property>
<name>dfs.data.dir</name>
<value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value>
</property>
</configuration>
2) Network configuration
[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restart
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311
tcp 0 0 ::ffff:127.0.0.1:54311 :::*
LISTEN
tcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311
ESTABLISHED
3) Starting Hadoop
[mahmood@tiger hadoop-1.0.2]$ stop-all.sh
Warning: $HADOOP_HOME is deprecated.
stopping jobtracker
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping tasktracker
no namenode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: no datanode to stop
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.sh
Warning: $HADOOP_HOME is deprecated.
starting namenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-namenode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting datanode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-datanode-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting secondarynamenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-secondarynamenode-tiger.out
starting jobtracker, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-jobtracker-tiger.out
localhost: Warning: $HADOOP_HOME is deprecated.
localhost:
localhost: starting tasktracker, logging to
/home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmoo
d-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps
21712 JobTracker
21882 TaskTracker
21580 SecondaryNameNode
21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -report
Warning: $HADOOP_HOME is deprecated.
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 0 time(s).
15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server:
localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Brahma Reddy Battula <br...@hotmail.com>.
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address) and server is not started with that port then client will retry ( and you will get following error..)..
I can able to trace that Namenode is not running From JPS report which you had posted..Please check the namenode logs ( location : /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>mapred.job.tracker</name> <value>localhost:54311</value></property><property> <name>mapred.child.java.opts</name> <value>-Xmx512m</value></property></configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>fs.default.name</name> <value>hdfs://localhost:54310</value></property></configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>dfs.replication</name> <value>1</value></property><property> <name>hadoop.tmp.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value></property><property> <name>dfs.name.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value></property><property> <name>dfs.data.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value></property></configuration>
2) Network configuration[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables# Firewall configuration written by system-config-firewall# Manual customization of this file is not recommended.*filter:INPUT ACCEPT [0:0]:FORWARD ACCEPT [0:0]:OUTPUT ACCEPT [0:0]-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT-A INPUT -p icmp -j ACCEPT-A INPUT -i lo -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT-A INPUT -j REJECT --reject-with icmp-host-prohibited-A FORWARD -j REJECT --reject-with icmp-host-prohibitedCOMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restartiptables: Flushing firewall rules: [ OK ]iptables: Setting chains to policy ACCEPT: filter [ OK ]iptables: Unloading modules: [ OK ]iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTENtcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHEDtcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop[mahmood@tiger hadoop-1.0.2]$ stop-all.shWarning: $HADOOP_HOME is deprecated.stopping jobtrackerlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: stopping tasktrackerno namenode to stoplocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: no datanode to stoplocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.shWarning: $HADOOP_HOME is deprecated.starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.outstarting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps21712 JobTracker21882 TaskTracker21580 SecondaryNameNode21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -reportWarning: $HADOOP_HOME is deprecated.15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Brahma Reddy Battula <br...@hotmail.com>.
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address) and server is not started with that port then client will retry ( and you will get following error..)..
I can able to trace that Namenode is not running From JPS report which you had posted..Please check the namenode logs ( location : /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>mapred.job.tracker</name> <value>localhost:54311</value></property><property> <name>mapred.child.java.opts</name> <value>-Xmx512m</value></property></configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>fs.default.name</name> <value>hdfs://localhost:54310</value></property></configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>dfs.replication</name> <value>1</value></property><property> <name>hadoop.tmp.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value></property><property> <name>dfs.name.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value></property><property> <name>dfs.data.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value></property></configuration>
2) Network configuration[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables# Firewall configuration written by system-config-firewall# Manual customization of this file is not recommended.*filter:INPUT ACCEPT [0:0]:FORWARD ACCEPT [0:0]:OUTPUT ACCEPT [0:0]-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT-A INPUT -p icmp -j ACCEPT-A INPUT -i lo -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT-A INPUT -j REJECT --reject-with icmp-host-prohibited-A FORWARD -j REJECT --reject-with icmp-host-prohibitedCOMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restartiptables: Flushing firewall rules: [ OK ]iptables: Setting chains to policy ACCEPT: filter [ OK ]iptables: Unloading modules: [ OK ]iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTENtcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHEDtcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop[mahmood@tiger hadoop-1.0.2]$ stop-all.shWarning: $HADOOP_HOME is deprecated.stopping jobtrackerlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: stopping tasktrackerno namenode to stoplocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: no datanode to stoplocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.shWarning: $HADOOP_HOME is deprecated.starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.outstarting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps21712 JobTracker21882 TaskTracker21580 SecondaryNameNode21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -reportWarning: $HADOOP_HOME is deprecated.15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Brahma Reddy Battula <br...@hotmail.com>.
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address) and server is not started with that port then client will retry ( and you will get following error..)..
I can able to trace that Namenode is not running From JPS report which you had posted..Please check the namenode logs ( location : /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>mapred.job.tracker</name> <value>localhost:54311</value></property><property> <name>mapred.child.java.opts</name> <value>-Xmx512m</value></property></configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>fs.default.name</name> <value>hdfs://localhost:54310</value></property></configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>dfs.replication</name> <value>1</value></property><property> <name>hadoop.tmp.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value></property><property> <name>dfs.name.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value></property><property> <name>dfs.data.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value></property></configuration>
2) Network configuration[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables# Firewall configuration written by system-config-firewall# Manual customization of this file is not recommended.*filter:INPUT ACCEPT [0:0]:FORWARD ACCEPT [0:0]:OUTPUT ACCEPT [0:0]-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT-A INPUT -p icmp -j ACCEPT-A INPUT -i lo -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT-A INPUT -j REJECT --reject-with icmp-host-prohibited-A FORWARD -j REJECT --reject-with icmp-host-prohibitedCOMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restartiptables: Flushing firewall rules: [ OK ]iptables: Setting chains to policy ACCEPT: filter [ OK ]iptables: Unloading modules: [ OK ]iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTENtcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHEDtcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop[mahmood@tiger hadoop-1.0.2]$ stop-all.shWarning: $HADOOP_HOME is deprecated.stopping jobtrackerlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: stopping tasktrackerno namenode to stoplocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: no datanode to stoplocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.shWarning: $HADOOP_HOME is deprecated.starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.outstarting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps21712 JobTracker21882 TaskTracker21580 SecondaryNameNode21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -reportWarning: $HADOOP_HOME is deprecated.15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood
RE: ipc.Client: Retrying connect to server
Posted by Brahma Reddy Battula <br...@hotmail.com>.
Hello Mahmood Naderan,
When client is trying to connect to server with configured port(and address) and server is not started with that port then client will retry ( and you will get following error..)..
I can able to trace that Namenode is not running From JPS report which you had posted..Please check the namenode logs ( location : /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.out/log)
Date: Fri, 17 Apr 2015 08:22:12 +0000
From: nt_mahmood@yahoo.com
To: user@hadoop.apache.org
Subject: ipc.Client: Retrying connect to server
Hello,I have done all steps (as far as I know) to bring up the hadoop. However, I get the this error
15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
There are a lot of threads and posts regarding this error and I tried them. However still stuck at this error :(
Can someone help me? What did I wrong?
Here are the configurations:
1) Hadoop configurations[mahmood@tiger hadoop-1.0.2]$ cat conf/mapred-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>mapred.job.tracker</name> <value>localhost:54311</value></property><property> <name>mapred.child.java.opts</name> <value>-Xmx512m</value></property></configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/core-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>fs.default.name</name> <value>hdfs://localhost:54310</value></property></configuration>
[mahmood@tiger hadoop-1.0.2]$ cat conf/hdfs-site.xml<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?><!-- Put site-specific property overrides in this file. --><configuration><property> <name>dfs.replication</name> <value>1</value></property><property> <name>hadoop.tmp.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/tmp</value></property><property> <name>dfs.name.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/name</value></property><property> <name>dfs.data.dir</name> <value>/home/mahmood/bigdatabench/apache/hadoop-1.0.2/folders/data</value></property></configuration>
2) Network configuration[root@tiger hadoop-1.0.2]# cat /etc/sysconfig/iptables# Firewall configuration written by system-config-firewall# Manual customization of this file is not recommended.*filter:INPUT ACCEPT [0:0]:FORWARD ACCEPT [0:0]:OUTPUT ACCEPT [0:0]-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT-A INPUT -p icmp -j ACCEPT-A INPUT -i lo -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 54310 -j ACCEPT-A INPUT -m state --state NEW -m tcp -p tcp --dport 54311 -j ACCEPT-A INPUT -j REJECT --reject-with icmp-host-prohibited-A FORWARD -j REJECT --reject-with icmp-host-prohibitedCOMMIT
[root@tiger hadoop-1.0.2]# /etc/init.d/iptables restartiptables: Flushing firewall rules: [ OK ]iptables: Setting chains to policy ACCEPT: filter [ OK ]iptables: Unloading modules: [ OK ]iptables: Applying firewall rules: [ OK ]
[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54310[mahmood@tiger hadoop-1.0.2]$ netstat -an | grep 54311tcp 0 0 ::ffff:127.0.0.1:54311 :::* LISTENtcp 426 0 ::ffff:127.0.0.1:54311 ::ffff:127.0.0.1:49639 ESTABLISHEDtcp 0 0 ::ffff:127.0.0.1:49639 ::ffff:127.0.0.1:54311 ESTABLISHED
3) Starting Hadoop[mahmood@tiger hadoop-1.0.2]$ stop-all.shWarning: $HADOOP_HOME is deprecated.stopping jobtrackerlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: stopping tasktrackerno namenode to stoplocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: no datanode to stoplocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: stopping secondarynamenode
[mahmood@tiger hadoop-1.0.2]$ start-all.shWarning: $HADOOP_HOME is deprecated.starting namenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-namenode-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting datanode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-datanode-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting secondarynamenode, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-secondarynamenode-tiger.outstarting jobtracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-jobtracker-tiger.outlocalhost: Warning: $HADOOP_HOME is deprecated.localhost:localhost: starting tasktracker, logging to /home/mahmood/bigdatabench/apache/hadoop-1.0.2/libexec/../logs/hadoop-mahmood-tasktracker-tiger.out
[mahmood@tiger hadoop-1.0.2]$ jps21712 JobTracker21882 TaskTracker21580 SecondaryNameNode21989 Jps
[mahmood@tiger hadoop-1.0.2]$ hadoop dfsadmin -reportWarning: $HADOOP_HOME is deprecated.15/04/17 12:45:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).15/04/17 12:45:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
Regards,
Mahmood