<div dir="ltr">Hi David<div><br></div><div>Thanks a lot for the quick reply! Yeah you are right, it was fine when I killed the process.</div><div>I'm very new to RabbitMQ, but wouldn't be better if the message was clearly pointing that out?</div>
<div><br></div><div>Thanks a gain</div><div>Mutaz</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, May 18, 2010 at 4:24 PM, David Wragg <span dir="ltr"><<a href="mailto:david@rabbitmq.com">david@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Mutaz,<br>
<div class="im"><br>
Mutaz Qasem <<a href="mailto:mutazmq@gmail.com">mutazmq@gmail.com</a>> writes:<br>
> This is the error output I get in the terminal when I do sudo<br>
> rabbitmq-server:<br>
><br>
> {error_logger,{{2010,5,18},{<br>
> 15,23,48}},"Protocol: ~p: register error:<br>
> ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name}},[{inet_tcp_dist,listen,1},{net_kernel,start_protos,4},{net_kernel,start_protos,3},{net_kernel,init_node,2},{net_kernel,init,1},{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}]}<br>
<br>
</div>This error means that another Erlang node with the same name is<br>
already running. Which probably means that rabbitmq-server is already<br>
running. Stop the existing rabbit process (probably by just killing<br>
it, if its origin is a mystery), and it should resolve this error.<br>
<br>
David<br>
<font color="#888888"><br>
--<br>
David Wragg<br>
Staff Engineer, RabbitMQ<br>
SpringSource, a division of VMware<br>
</font></blockquote></div><br></div></div>