[rabbitmq-discuss] Clustering on different interface
Tim Watson
tim at rabbitmq.com
Wed Jun 19 16:44:37 BST 2013
Just to follow up, since it's been suggested that what you were asking is how to make *clustering* listen on 10.10.10.x1, you'll need to add the following to your config file instead:
[
{rabbit, [{tcp_listeners, [{"192.168.1.x1", 5672}]}]},
{kernel, [{inet_dist_use_interface, {10,10,10,1}}]}
].
On 19 Jun 2013, at 16:20, Tim Watson wrote:
> On 19 Jun 2013, at 14:34, andiconstantin wrote:
>
>> Hi!
>>
>> I have 2 rabbit servers, rabbit1 and rabbit2.
>> For rabbit1 I have two interfaces 192.168.1.x1 and 10.10.10.x1 and for
>> rabbit2 i have 192.168.1.x2 and 10.10.10.x2.
>> I can make the cluster on the 192.168.1.X interfaces but i cannot make-it on
>> the 10.10.10.X interfaces.
>> The 10.10.10.X intarfaces are directly connected and i wanna use them
>> because they do not depend on a switch.
>> I have all the addresses in /etc/hosts with different names.
>> I also added listeners in /etc/rabbitmq/rabbitmq.config
>>
>> [
>> {rabbit, [
>> {tcp_listeners,[{"192.168.1.x1",5672},
>> {"10.10.10.x1",5672}]}
>> ]}
>>
>
> I think you're getting confused between TCP listeners (which listen for AMQP connections) and clustering, which does not use the tcp_listeners configuration element but works via the Erlang Port Mapper Daemon - see http://www.erlang.org/doc/man/epmd.html.
>
> Cheers,
> Tim
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
More information about the rabbitmq-discuss
mailing list