It is possible that this is an issue that has already been fixed and the
solution will be included in the next release. The console output from
the first attempt to start the broker will confirm this. Does it contain
the string "transform_failed_previously"? If it doesn't then this is a
different issue and in this case the contents of
/var/lib/rabbitmq/mnesia/ will be useful to determine the cause and to
fix it.
The supplied console is from the second attempt to start the broker
after upgrading.
An interim workaround until a next releases that fixes the problem would
be to move the contents of /var/lib/rabbitmq/mnesia/rabbit@uni and the
*-upgrade-backup folder to some place safe. All persistent messages and
broker configuration (such as persistent queues, exchanges, users) will
be lost through this workaround.
--
Emile Joubert
RabbitMQ
SpringSource, a division of VMware
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
