[rabbitmq-discuss] fail upgrade from 3.1.3 to 3.1.4

Thu Aug 8 16:49:21 BST 2013

Hy Simon,

Sorry but my knowledge of mnesia, erlang is close to nothing so I dont
understand your answer. My goal is to extract message and put them back un
RabbitMQ.
I know nothing about erlang, do you please tell my how to extract message.
If I have datas I can arrange them in json to use RabbitMQ submit api.

Thank you for your help.

2013/8/8 Simon MacMullen <simon at rabbitmq.com>

> You can pull records out of Mnesia, but bear in mind that messages are
> stored in RabbitMQ's message store, not Mnesia. And really RabbitMQ is the
> only thing that can read that in a practical sense.
>
> Cheers, Simon
>
>
> On 08/08/2013 1:08PM, Guillaume Vernat wrote:
>
>> Ok. I will try and let you know...
>>
>> And my other question is there a way to export datas from mnesia db ?
>>
>>
>> 2013/8/8 Simon MacMullen <simon at rabbitmq.com <mailto:simon at rabbitmq.com>>
>>
>>
>>     Hi.
>>
>>     It looks like we managed to release a version 3.1.4 which is not
>>     compatible with other 3.1.x versions in the same cluster. Damn.
>>
>>     So if you upgrade *all* the nodes in the cluster to 3.1.4, and
>>     restore the /var/lib/rabbitmq/mnesia on all the nodes, then things
>>     should work.
>>
>>     Cheers, Simon
>>
>>
>>     On 08/08/2013 11:54AM, Guillaume Vernat wrote:
>>
>>         Hy Simon,
>>
>>         I really needed this cluster up. So, after making a copy of
>>         /var/lib/rabbitmq/mnesia I rebuild cluster.
>>         Now it's ok going on 3.1.4
>>
>>         How can I export messages from the copy in order to have them
>>         back in
>>         the cluster ?
>>
>>         Guillaume VERNAT
>>
>>
>>         2013/8/8 Guillaume Vernat <verenate at verenate.com
>>         <mailto:verenate at verenate.com>
>>         <mailto:verenate at verenate.com <mailto:verenate at verenate.com>**
>> >__>
>>
>>
>>
>>              Hy Simmons, thank you for your answer.
>>
>>              The cluster was : amqp105/amqp107 and amqp108 (ram). Main
>>         node is
>>              105 and I stated update with it.
>>              107 and 108 were runnning during update. I join the log file
>>              starting errors where :
>>
>>              Error description:
>>                  {error,{incompatible_bytecode,**__"Incompatible Erlang
>>
>>         bytecode
>>              found on nodes"}}
>>
>>
>>
>>
>>              2013/8/8 Simon MacMullen <simon at rabbitmq.com
>>         <mailto:simon at rabbitmq.com>
>>              <mailto:simon at rabbitmq.com <mailto:simon at rabbitmq.com>>>
>>
>>
>>
>>                  Huh. You should not need to stop the cluster to do a
>> minor
>>                  version upgrade like that. What error are you seeing?
>>
>>                  Cheers, Simon
>>
>>
>>                  On 08/08/2013 9:25AM, Guillaume Vernat wrote:
>>
>>                      Hy,
>>
>>                      I try to up upgrade a cluster from 3.1.3 to 3.1.4
>>         on debian
>>                      wheezy.
>>                      apt-get update
>>                      apt-get dist-upgrade
>>
>>                      but upgrade fail because I did not stop the cluster
>>         nodes :(
>>                      I finally stop the other cluster nodes but it was
>>         too late
>>                      for the first
>>                      one.
>>
>>                      How can I start back the first node ?
>>                      I already touch
>>
>>         /var/lib/rabbitmq/mnesia/<____**node>/nodes_running_at_____**
>> shutdown,
>>
>>
>>                      rabbit_serial, cluster_nodes.config but it fail
>> again.
>>
>>                      Guillaume
>>
>>
>>                      ______________________________**
>> _____________________
>>                      rabbitmq-discuss mailing list
>>                      rabbitmq-discuss at lists.__rabbi**__tmq.com<http://rabbi__tmq.com>
>>         <http://rabbitmq.com>
>>                      <mailto:rabbitmq-discuss at __lis**ts.rabbitmq.com<http://lists.rabbitmq.com>
>>         <mailto:rabbitmq-discuss@**lists.rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
>> >>
>>         https://lists.rabbitmq.com/___**_cgi-bin/mailman/listinfo/____**
>> rabbitmq-discuss<https://lists.rabbitmq.com/____cgi-bin/mailman/listinfo/____rabbitmq-discuss>
>>         <https://lists.rabbitmq.com/__**cgi-bin/mailman/listinfo/__**
>> rabbitmq-discuss<https://lists.rabbitmq.com/__cgi-bin/mailman/listinfo/__rabbitmq-discuss>
>> >
>>
>>
>>
>>         <https://lists.rabbitmq.com/__**cgi-bin/mailman/listinfo/__**
>> rabbitmq-discuss<https://lists.rabbitmq.com/__cgi-bin/mailman/listinfo/__rabbitmq-discuss>
>>         <https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**
>> rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>> >>
>>
>>
>>                  --
>>                  Simon MacMullen
>>                  RabbitMQ, Pivotal
>>
>>
> --
> Simon MacMullen
> RabbitMQ, Pivotal
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130808/565dc9f8/attachment.htm>