[rabbitmq-discuss] DNS Issues / Error: cannot_get_pid

[Matthew Sackman]

Hi Michael,

On Wed, Nov 11, 2009 at 01:32:47PM +0100, Michael Elsdörfer wrote:
> 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.

That's weird. What happens if you just do "erl -sname foo at localhost" ?
Also, can you start up rabbit like this, and then do a ps ax | grep
rabbit - and check the sname param - for me (installing from a package),
I get "... -sname rabbit at localhost ..." and it does all work correctly.

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

Which version of Erlang are you using?

I have a vague recollection that -sname only used to allow the node part
of the node name, which tallies with what you're seeing, but I've tried
going back as far as R11B5 and it still works there. I've just had a
quick trawl through the Erlang release notes and can't find anything
there either. In fact, with R11B5, R12B3 and R13B02, if I try
erl -sname foo at bar@baz then it blows up with invalid hostname, whereas
erl -sname foo at bar works fine.

> 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.

Ahh yes, I remember having to use that rule in the past, though not for
Rabbit. Glad you've found a work around, but I'd quite like to dig into
why it's not working for you as I think it should.

Matthew