Steve,
I missed this part of the email.
So if I change the 0.0.0.0 to either the 192.168.1.102 or 103
depending on what is necessary will that solve the problem?
It looks like it lives in 10 places.
-John
On Jun 9, 2009, at 10:17 AM, Steve Loughran wrote:
> I have some other applications running on these machines, that
> communicate across the internal network and they work perfectly.
I admire their strength. Multihost systems cause us trouble. That
and machines that don't quite know who they are
http://jira.smartfrog.org/jira/browse/SFOS-5
https://issues.apache.org/jira/browse/HADOOP-3612
https://issues.apache.org/jira/browse/HADOOP-3426
https://issues.apache.org/jira/browse/HADOOP-3613
https://issues.apache.org/jira/browse/HADOOP-5339
One thing to consider is that some of the various services of Hadoop
are bound to 0:0:0:0, which means every Ipv4 address, you really
want to bring up everything, including jetty services, on the en0
network adapter, by binding them to 192.168.1.102; this will cause
anyone trying to talk to them over the other network to fail, which
at least find the problem sooner rather than later
