[erlang-questions] : Trouble connecting to Erlang in a virtual hosting setup
Tue Aug 21 14:11:46 CEST 2007
If you can find a name that is routable from both sides.
E.g in /etc/hosts on z13261AA.textdrive.com define
wagerlabs.com and topdog.cc to be alternative names for
Then start the Erlang node with -name name@REDACTED
An Erlang node must have one hostname, so if you need
to contact topdog.cc you probably need to start another node.
There are kernel variables to control which ports the
Erlang distribution protocol should listen to. If you
have a firewall you will need to use these to know
which port range (plus EPMD) to open.
On Tue, Aug 21, 2007 at 02:49:44AM -0700, Jason A. Hoffman wrote:
> On Aug 21, 2007, at 2:28 AM, Joel Reymont wrote:
> > I host with Joyent on one of their Sparc Accelerators. My container
> > has a dedicated IP address and I point both wagerlabs.com and
> > topdog.cc to it. Internally, though, the name of the box is
> > z13261AA.textdrive.com.
> > I cannot connect to this node with net_adm:ping/1 using the internal
> > box name since the Erlang ports are blocked.
> > The challenge code in dist_util grabs the internal box name and fails
> > in list_to_existing_atom when I cannot connect to my node using my
> > domain names or the IP address. It also fails with no_node if I pre-
> > create the xxx@REDACTED atom since the host portion of
> > the node name won't match that returned by the Erlang node at Joyent.
> > Is there a workaround for this?
> > Thanks, Joel
> It doesn't have to be called "z13261AA.textdrive.com".
> You can change the hostname with
> hostname something.com
> and permanently by editing /etc/nodename
> - Jason
> erlang-questions mailing list
/ Raimo Niskanen, Erlang/OTP, Ericsson AB
More information about the erlang-questions