[rabbitmq-discuss] Clustered server doesn't permit local connections

Eric Siroker esiroker at gmail.com
Wed May 23 19:14:04 BST 2012

On Wed, May 23, 2012 at 9:50 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
> It occurs when you bring up a new node in an existing cluster, and that node
> is sufficiently short of memory or disc space that the memory or disc space
> alarm goes off immediately.

I believe you're correct.  I increased the disk space available to
RabbitMQ so that it's above the low watermark and it's operating
correctly now.

Thanks for identifying the issue, Simon.


More information about the rabbitmq-discuss mailing list