[rabbitmq-discuss] DNS Issues / Error: cannot_get_pid

[Michael Elsdörfer]

Thanks for the response.

I actually managed to gather those settings on my own and had tried them
in the meantime - they don't seem to work (not in fixing the DNS-related
issue, anyway):

* With "NODENAME=rabbit at localhost" startup_log says "Starting node
rabbit at localhost@myhostname..."""

* Strangely, "rabbitmq-multi status" still references
"rabbit at myhostname", despite the NODENAME setting.

I'm using the Debian package from http://www.rabbitmq.com/debian/
(version 1.7.0-1).

I should say that I've since worked around the issue by configuring
iptables to pass all connections from the local interface through
(using: iptables -A INPUT -i lo -j ACCEPT), so it's not a showstopper
for me.

Michael

[FWIW, the process name missing in my initial mail is "init_gethost 4" -
though I've since noticed that the two instances of it are also running
when RabbitMQ started up successfully, so I suppose that's actually normal.]

Matthew Sackman schrieb:
> Michael,
> 
> On Fri, Nov 06, 2009 at 01:47:38PM +0100, Michael Elsdörfer wrote:
>> I wonder if there is another solution (I couldn't find one in the thread
>> above). Can't I tell rabbitmq to just bind to loopback? It's really only
>> supposed to run locally.
> 
> Indeed. In your /etc/rabbitmq/rabbitmq.conf, add the line:
> 
> NODENAME=rabbit at localhost
> 
> This will force Erlang to not look at your hostname when trying to
> determine its node name, and instead will use localhost. Note though
> that this means the *Erlang node* is not contactable via a different
> machine (i.e. you couldn't use rabbitmqctl from a different machine, or
> do clustering). Also node it does not stop *Rabbit* from listening on
> public interfaces. If you want to make sure Rabbit only listens to
> 127.0.0.1 then add a further line to your rabbitmq.conf:
> 
> NODE_IP_ADDRESS=127.0.0.1
> 
> I hope that's of help.
> 
> Matthew