[rabbitmq-discuss] RabbitMQ won't start on RHEL 6.1

Sun Jul 10 20:38:46 BST 2011

If you are sure you don't have any other Erlang application running on your system that may depend on epmd running then you can try by stopping it and starting RabbitMQ afterwards.

On Jul 10, 2011, at 9:37 PM, Dana Rea wrote:

> On Sun, Jul 10, 2011 at 3:32 PM, Alvaro Videla <videlalvaro at gmail.com> wrote:
> If you do:
> 
> ps ax | grep rabbit
> 
> Do you get any process running? 
> 
> No, I've been careful to check for running Rabbit processes before trying to start it. 
> 
> BTW, the port 5672 is not the EPMD default one, so that's very strange.
> 
> Hmm, perhaps I'm mistaken then. netstat just reports 0.0.0.0:epmd, so 5672 may not already be in use, netstat doesn't list that number for anything else. 
> 
> -Alvaro
> 
> On Jul 10, 2011, at 9:29 PM, Dana Rea wrote:
> 
>> I have, netstat -tlp tells me that it's epmd running on port 5672. Rabbit still doesn't start if I kill all processes running on that port beforehand.
>> 
>> I'm not familiar with Erlang, but it it possible that Rabbit is trying to listen on the same port as epmd? Although, starting epmd on another port didn't help either.
>> 
>> On Sun, Jul 10, 2011 at 3:22 PM, Alvaro Videla <videlalvaro at gmail.com> wrote:
>> Hi
>> 
>> > =ERROR REPORT==== 9-Jul-2011::17:11:50 ===
>> > failed to start TCP Listener on 0.0.0.0:5672 - eaddrinuse
>> 
>> I think that tells that RabbitMQ is already running in your machine or that at least you have a service that is already using that address.
>> 
>> Try checking that there's no version of the broker already running.
>> 
>> -Alvaro
>> 
>> 
>> 
>> 
>> -- 
>>  Dana
> 
> Sent form my Nokia 1100
> 
> 
> 
> 
> 
> 
> -- 
>  Dana

Sent form my Nokia 1100

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110710/b640179c/attachment.htm>