[rabbitmq-discuss] Set rabbitmq to use in Amazon EC2 with different regions

Jason McIntosh mcintoshj at gmail.com
Mon Jul 22 20:05:01 BST 2013


Not enough info... though one quick guess - are you sure you don't have
another process running on that port?  Do a netstat -an |grep 5672.  As I
recall, a lot of linux installations now include QPID or something like
that which runs on that port.  Note, rabbit WILL start even with firewall
rules turned on - linux itself just won't allow external connections.

Jason


On Mon, Jul 22, 2013 at 12:38 PM, Pedro Sá da Costa <psdc1978 at gmail.com>wrote:

> Hi,
>
> I am trying to configure rabbitmq with EC2. The rabbitmq works when it
> uses the private IP, but when I try to use the public IP, I can't start the
> rabbitmq. What I want to do is that different EC2 regions access the same
> rabbitmq. E.g.: the rabbitmq is running in region USA, and the applications
> are running in Singapore and in Ireland. The applications must access the
> rabbitmq in USA. I open all the ports in the regions.
>
> The configuration file that I use is:
>
> $ cat /etc/rabbitmq/rabbitmq-env.conf
> RABBITMQ_NODE_IP_ADDRESS=XX.XXX.XX.XXX
>
>
> The error that I get is:
>
> $ cat /var/log/rabbitmq/startup_log
>
>               RabbitMQ 3.1.3. Copyright (C) 2007-2013 VMware, Inc.
>   ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
>   ##  ##
>   ##########  Logs: /var/log/rabbitmq/rabbit at ip-10-170-74-198.log
>   ######  ##        /var/log/rabbitmq/rabbit at ip-10-170-74-198-sasl.log
>   ##########
>               Starting broker...
>
> BOOT FAILED
> ===========
>
> Error description:
>    {could_not_start_tcp_listener,{"XX.XXX.XX.XXX",5672}}
>
> Log files (may contain more information):
>    /var/log/rabbitmq/rabbit at ip-10-170-74-198.log
>    /var/log/rabbitmq/rabbit at ip-10-170-74-198-sasl.log
>
> Stack trace:
>    [{rabbit_networking,start_listener0,4,[]},
>     {rabbit_networking,'-start_listener/4-lc$^0/1-0-',4,[]},
>     {rabbit_networking,start_listener,4,[]},
>     {rabbit_networking,'-boot_tcp/0-lc$^0/1-0-',1,[]},
>     {rabbit_networking,boot_tcp,0,[]},
>     {rabbit_networking,boot,0,[]},
>     {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},
>     {rabbit,run_boot_step,1,[]}]
>
>
>
> BOOT FAILED
> ===========
>
> Error description:
>    {could_not_start,rabbit,
>        {bad_return,
>            {{rabbit,start,[normal,[]]},
>             {'EXIT',
>                 {rabbit,failure_during_boot,
>
> {could_not_start_tcp_listener,{"XX.XXX.XX.XXX",5672}}}}}}}
>
> Log files (may contain more information):
>    /var/log/rabbitmq/rabbit at ip-10-170-74-198.log
>    /var/log/rabbitmq/rabbit at ip-10-170-74-198-sasl.log
>
> {"init terminating in
> do_boot",{rabbit,failure_during_boot,{could_not_start,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot,{could_not_start_tcp_listener,{"XX.XXX.XX.XXX",5672}}}}}}}}}
>
> How can I set the rabbitmq to use the public IP for other regions access
> it?
>
> --
> Best regards,
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>


-- 
Jason McIntosh
http://mcintosh.poetshome.com/blog/
573-424-7612
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130722/95ec7994/attachment.htm>


More information about the rabbitmq-discuss mailing list