[rabbitmq-discuss] RabbitMQ crashing upon starting with a clustering setup on EC2

Thu Feb 7 16:08:34 GMT 2013

Someone replied to me off list, I just had to remove .ec2.internal from the 
hostnames and pre-pend them with rabbit@

Thanks


On Wednesday, February 6, 2013 11:52:05 AM UTC-5, mdo... at engineyard.com 
wrote:
>
> I'm trying to cluster 2 nodes on EC2.  I have the erlang cookie in place 
> on both instances and I verified this.  Both instances have the same 
> rabbitmq.config file:
>
> [
>   {rabbit, [
>     {cluster_nodes, 
> ['ip-10-114-25-195.ec2.internal','ip-10-158-69-124.ec2.internal']},
>     {default_user, <<"guest">>},
>     {default_pass, <<"guest">>}
>   ]}
> ].
>
> When I try to start up a single node, I get the following crash report in 
> the log:  
>
> =CRASH REPORT==== 6-Feb-2013::11:38:00 ===
>   crasher:
>     initial call: application_master:init/4
>     pid: <0.112.0>
>     registered_name: []
>     exception exit: {bad_return,{{rabbit,start,[normal,[]]},
>                                  {'EXIT',{rabbit,failure_during_boot}}}}
>       in function  application_master:init/4
>     ancestors: [<0.111.0>]
>     messages: [{'EXIT',<0.114.0>,normal}]
>     links: [<0.111.0>,<0.7.0>]
>     dictionary: []
>     trap_exit: true
>     status: running
>     heap_size: 2584
>     stack_size: 24
>     reductions: 245
>   neighbours:
>
> Everything works fine when I pull out the cluster_nodes configuration. 
>  I'm not quite sure what I'm doing wrong.  I've also tried using rabbit1, 
> rabbit2 as hostnames with /etc/hosts mapped to their internal IP address 
> but ran into the same issue.  Any help would be greatly appreciated.
>
> Thanks!
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130207/9bbdb2c6/attachment-0001.htm>