search

linearregression / hypertable

Automatically exported from code.google.com/p/hypertable
GNU General Public License v2.0
0 stars 0 forks source link

network sanity checker #112

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
In investigating a problem encountered by William Sylvester (see
http://groups.google.com/group/hypertable-user/browse_thread/thread/570e32f6930a
c6f9),
we discovered that there was a bad hostname mapping in /etc/hosts that was
causing problems.  The entry looked like this:

192.107.200.121 ht-prot1.pseuds.com

But the real address of the host was supposed to be 198.107.200.121.  This
was causing a bad IP address to get written into Hyperspace under
/hypertable/master:address.  serverup was unable to ping the master.  The
connection request was getting routed off into la la land.

We should come up with a basic network sanity check that resolves each
local host name and has every other host attempt to connect to each other
using the resolved IP address.  It should read hypertable.cfg and set up
echo services on all of the basic service addresses to make sure that they
can all properly talk to one another (including UDP ports as well).  It
would be good to have the test servers just run the comm layer so that all
of the application code is not in the picture.

Original issue reported on code.google.com by nuggetwh...@gmail.com on 18 Jun 2008 at 6:59

GoogleCodeExporter commented 9 years ago 
Quite a nasty one actually. I have a hosting company that didn't map stuff 
correctly. Took me a couple of days to 
figure out. Maybe up the awareness on this bug.

-- Josh

Original comment by joshua.c...@gmail.com on 1 Dec 2008 at 5:54

GoogleCodeExporter commented 9 years ago

Original comment by nuggetwh...@gmail.com on 11 Apr 2010 at 9:13

GoogleCodeExporter commented 9 years ago

Original comment by nuggetwh...@gmail.com on 12 Jan 2011 at 9:46

GoogleCodeExporter commented 9 years ago 
This test should also verify that traffic to all ports are not being blocked by 
a firewall.

Original comment by nuggetwh...@gmail.com on 10 Feb 2011 at 7:59

GoogleCodeExporter commented 9 years ago

Original comment by nuggetwh...@gmail.com on 14 Jan 2012 at 8:32