RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

When trying to create a simple 2 node RabbitMQ cluster, it always fails with a "nodedown" message on the node trying to join the other node's cluster.

Logged on that "client" node :

avc:  denied  { name_connect } for  pid=3433 comm="beam.smp" dest=25672 scontext=system_u:system_r:rabbitmq_t:s0 tcontext=system_u:object_r:amqp_port_t:s0 tclass=tcp_socket

Once this is allowed, the "rabbitmqctl join_cluster rabbit@remotehost" command succeeds and the cluster is properly created.

This is RHEL 7.1 with 3.13.1-23.el7 (and using the latest Fedora erlang and rabbitmq rebuilt for RHEL7).

Actually, the above might be incomplete, since I noticed after creating this report that *I* had added the amqp_port_t type for tcp port 25672...

# semanage port -l -C
SELinux Port Type              Proto    Port Number

amqp_port_t                    tcp      25672, 15672

I think I did that to be able to have rabbitmq bind to those ports, as 15672 is the default port for the included rabbitmq_management plugin's web interface and 25672 is the default RABBITMQ_NODE_PORT used for clustering.

So at this point I'm not sure I did the right thing. What I do know is that it would be good to have RabbitMQ be able to bind to those two ports by default *and* be able to name_connect to 25672.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2300.html