[rabbitmq-discuss] rabbitmqctl -n ..... status fails one way but not the other

Emile Joubert emile at rabbitmq.com
Thu Feb 9 11:06:38 GMT 2012


On 08/02/12 17:25, davidib wrote:
> Basically, I can "rabbitmqctl -n rabbit at A status" while on node B (and
> properly see rabbitmq node on A), but "rabbitmqctl -n rabbit at B status"
> while on machine A reports the node on B is not running.

This might be a firewall issue. Check whether you can establish a TCP
connection to port 1052 on node B from node A. Running a cluster across
firewalls (outside a datacentre) or over unreliable network links is not
recommended. For more information see:


More information about the rabbitmq-discuss mailing list