Please see what I said in that thread:
http://permalink.gmane.org/gmane.comp.networking.rabbitmq.general/18295
The assertion that the hostname needs to resolve to 127.0.0.1 via
/etc/hosts is untrue. The hostname needs to resolve to an IP address of
the machine, via DNS or /etc/hosts or whatever.
Umm, with the shell fragment posted, you have the receiver started
outside the while true loop. Therefore the shell will never start the
receiver, and messages back up inside RabbitMQ until memory is
exhausted.
You can verify this with rabbitmqctl list_queues or the management
plugin web UI.
--
We believe this to be fixed in the upstream Debian package:
http://lists.rabbitmq.com/pipermail/rabbitmq-
announce/attachments/20120319/e92146ee/attachment.txt
(I don't think there was ever a Debian bug for this but it was addressed
in RabbitMQ 2.8.0.)
--
You received this bug notification
So it sounds like NetworkManager is making changes to /etc/hosts that
are confusing Rabbit. To help figure out if this is the problem, can
anyone experiencing this on 11.10 tell me:
* What does ping ${hostname} look like when networking is up?
* What does ping ${hostname} look like when
Sorry, I mean ping $(hostname), with round brackets. Duh.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/670289
Title:
Laptop won't shut down with rabbitmq running
To
