[rabbitmq-discuss] FYI: RabbitMQ default installation broken on Ubuntu (potential all Debian-likes)

René Gallati regal at nine.ch
Mon Sep 10 12:31:19 BST 2012

On 09/07/2012 07:10 PM, Simon MacMullen wrote:
> On 07/09/12 16:42, René Gallati wrote:
>> There are some subtle differences here. The machine has a perfect
>> resolvable hostname. The difference is, if the hostname does NOT resolve
>> to (which I expect is pretty much standard) then it does not
>> work.
> This really is not what I'm seeing here, honestly. Can you send me the
> contents of /var/rabbitmq/log when it fails to start?
> Cheers, Simon

I spent some time playing with my personal systems over the weekend 
where everything worked great. I could trace the problem back to the 
firewall config opening up the ports too late which causes 
rabbitmq-server not to be able to connect to itself and lets the 
installation abort.

So it boils down to a race condition, or rather a wrong sequence of 
installation / setting up which causes a failure in the start of 
rabbitmq-server and not a broken package/installer. We have a relative 
restrictive default firewall policy and it just bit back.

Sorry to having caused a fuzz.

While trying to fix this I found that I basically have to allow all 
traffic on $extip since it appears that beam.smp is binding 2 random 
ports and needs to be accessible there, is that correct? Ie. just 
allowing 4369 and 5672 the latter of which btw. is the only port it 
binds as ipv6 is not enough. Rabbitmq starts but hangs while starting 
and the init script never returns until I allow access to the randomly 
bound ports. Can I pre-set these ports with some configuration directive 
or are they truly random?



More information about the rabbitmq-discuss mailing list