[rabbitmq-discuss] Upgrading of RabbitMq clusters connected with federation plugin from 2.8.7 to version 3.1.0

[Viraj Gupte]

This is the configuration of shovel plugin I wish to run on Rabbitmq 2.8.7.
The ip address of the machine that declares the shovel plugin is
10.33.32.130.
[
{kernel, [{inet_dist_listen_min, 4001}, {inet_dist_listen_max, 4004}]},
{rabbitmq_shovel,
  [ {shovels, [ {MQ_shovel,
                 [ { sources,
                      [{broker, "amqp://"}
                         ]}

              ,{destinations,
                [ {broker, "amqp://10.33.32.131:5672"}
                               ]}
                   ,{queue,<<"outbound.q">>}
                   ,{prefetch_count,10}
                   ,{ack_mode,on_confirm}
                   ,{publish_properties,[{delivery_mode,2}]}
                   ,{reconnect_delay,5}
                   ]}

                 ]}
              ]}

].


As soon as I try to start the server after configuration, I get this error
in logs:
{"could not start kernel pid",application_controller,"error in config file
\"/etc/rabbitmq/rabbitmq.config\" (1): bad term"}


On Mon, Oct 21, 2013 at 9:55 AM, Viraj Gupte <viraj.gupte at credorax.com>wrote:

> Yeah, thats what I realised when I did the upgrade, the type x-federation
> wasnt there. I had to set a policy to make it work
>
>
> On Mon, Oct 21, 2013 at 5:45 AM, Simon MacMullen <simon at rabbitmq.com>wrote:
>
>> On 17/10/2013 3:41PM, Viraj Gupte wrote:
>>
>>> Hi All,
>>> I have two rabbitmq clusters A and B connected to each other via
>>> federation plugin in bidirectional manner.Both of them run version 2.8.7.
>>>   I am planning to upgrade  cluster A to 3.1.0 to check how federation
>>> works with the cluster with 2.8.7 version(cluster B).
>>> What should be my approach so as to keep the federation config intact on
>>> cluster A along with messages and queues
>>>
>>
>> Federation does not require that brokers be the same version. So you can
>> upgrade clusters A and B at different times.
>>
>> Note that the federation configuration mechanism changed in 3.0.0 so you
>> will need to redo the federation config in each cluster as you upgrade it;
>> see http://www.rabbitmq.com/blog/**2012/11/19/breaking-things-**
>> with-rabbitmq-3-0/<http://www.rabbitmq.com/blog/2012/11/19/breaking-things-with-rabbitmq-3-0/>
>>
>> Cheers, Simon
>>
>> --
>> Simon MacMullen
>> RabbitMQ, Pivotal
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131021/de051d46/attachment.htm>