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

Ceri Storey ceri at lshift.net
Wed Jul 24 12:42:41 BST 2013


(22/07/13 18:38), Pedro Sá da Costa 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.

As has been said elsewhere in this thread, you don't need to change
anything to be able to access the Rabbit via it's public address. On Ec2
at least, your machine itself is given the private IP, and the
translation to and from the public IP is handled by Amazon's networking
devices.

Did you have problems trying connect to the rabbit via it's public IP
when you were using it's default configuration?

>
> 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

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


More information about the rabbitmq-discuss mailing list