Move rabbit's clustering port away from the ephemeral port range
authorMichele Baldessari <michele@acksyn.org>
Fri, 22 Jul 2016 06:40:25 +0000 (08:40 +0200)
committerMichele Baldessari <michele@acksyn.org>
Fri, 16 Sep 2016 16:19:04 +0000 (18:19 +0200)
commita1dcc16f3addd43c229553706b2ba080cde7ea31
tree0c54ac72d8dbae94ef61377c8a59d5b26f2d2bb7
parent89f9a3f2e0274169f305a503f642867ef14244e1
Move rabbit's clustering port away from the ephemeral port range

Currently RabbitMQ cluster uses a predefined port 35672 for clustering.
This port belongs to so-called ephemeral ports range.

Ephemeral ports are the ports kernel assings to application if it
doesn't specify which port to open. So there is a small chance that this
application being started before RabbitMQ itself could grab this port.
While rather unlikely we did see this happen.

Selinux change should already be in place. On my Centos 7 we have:
rabbitmq_port_t                tcp      25672
corenet_tcp_bind_rabbitmq_port(rabbitmq_t)
corenet_tcp_connect_rabbitmq_port(rabbitmq_t)

First noted via:
https://bugzilla.redhat.com/show_bug.cgi?id=1357522

Closes-Bug: #1623818

Depends-On: I0bcd0d063a7a766483426fdd5ea81cbe1dfaa348
Change-Id: I995bd96c2a17614e954ea5bbae4d58998ef420dc
puppet/services/rabbitmq.yaml