Nodes fail to communicate with peers in AWS Autoscaling Group about rabbitmq-autocluster HOT 3 CLOSED

Thank you for your time.

Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. This assumes we have a certain amount of information to work with.

We get at least a dozen of questions through various venues every single day, often quite light on details.
At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because of that questions, investigations, root cause analysis, discussions for potential features are all considered to be mailing list material by our team. Please post this to rabbitmq-users.

Getting all the details necessary to make a conclusion or even form a hypothesis about what's happening can take a fair amount of time. Please help others help you by providing as much relevant information as possible on the list:

• Server and client versions used
• Server logs
• A code example or terminal transcript that can be used to reproduce
• Full exception stack traces (not a single line message)
• rabbitmqctl status (and, if possible, rabbitmqctl environment output)
• Other relevant things about the environment and workload, e.g. a traffic capture

Feel free to edit out hostnames and other potentially sensitive information.

When/if we have enough details and evidence we'd be happy to file a new issue.

Thanks you.

from rabbitmq-autocluster.

This plugin does its job according to the log: it does discover a peer, which means another peer did register successfully.

Inter-node connectivity is in no way affected by this plugin. Please move this to rabbitmq-users.

from rabbitmq-autocluster.

Generally there are three things needed for nodes to successfully cluster with each other:

• They can resolve each other's hostnames
• They can resolve their own hostnames the same way their peers can (A contacts B and B believes its hostname is the same as specified by A)
• Their Erlang cookies match

Nodes use port 25672 for inter-node communication by default and you have it open, as well as 4369 for the port mapping daemon.

Take a look at the log files on all nodes, there may be clues.

from rabbitmq-autocluster.