I get the same error sometimes, although everything seems to work fine after that, even though it gives that error, so it's probably not a problem.

- Matt Zytaruk


Michael Taggart wrote:

I've followed the steps in the media-style wiki for setting up a map
reduce system. I am only having one strange error when I attempt to
start the tasktrackers. Here is my output:

[EMAIL PROTECTED] nutch]# bin/nutch-daemon.sh start tasktracker
starting tasktracker, logging
to /usr/local/nutch/nutch-root-tasktracker-srv08.xxxxx.com.log
051214 133808 parsing file:/usr/local/nutch/conf/nutch-default.xml
051214 133808 parsing file:/usr/local/nutch/conf/nutch-site.xml
051214 133808 Server listener on port 50050: starting
051214 133808 Server handler 0 on 50050: starting
051214 133808 Server handler 1 on 50050: starting
051214 133808 Server listener on port 50040: starting
051214 133808 Server handler 0 on 50040: starting
051214 133808 Server handler 1 on 50040: starting
java.net.ConnectException: Connection refused
       at java.net.PlainSocketImpl.socketConnect(Native Method)

I have configured my nutch-site.xml as follows on each box:
?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="nutch-conf.xsl"?>

<!-- Put site-specific property overrides in this file. -->

<nutch-conf>
<property>
 <name>fs.default.name</name>
 <value>srv05.xxxxx.com:50000</value>
 <description>The name of the default file system.  Either the
 literal string "local" or a host:port for NDFS.</description>
</property>
<property>
 <name>mapred.job.tracker</name>
 <value>srv05.xxxxx.com:50020</value>
 <description>The host and port that the MapReduce job tracker runs
 at.  If "local", then jobs are run in-process as a single map
 and reduce task.
 </description>
</property>
</nutch-conf>

srv05 is my namenode and jobtracker. That server starts up the namenode
and jobtracker services just fine. Maybe I am supposed to reference
fs.default.name as srv08:50000 on srv08? I thought from reading the
mediawiki that I need to reference my BoxA on every other machine.
No firewall on this internal network so I am wondering why I am getting
a connection refused. Anyone have any ideas?
Thanks,
Mike



Reply via email to