On updating a el5 machine yesterday, I got the rabbitmq-server update from 2.0 to 2.1 This resulted in: 1. rabbitmq-server shutting down during update - as far as I know this is a no-go? 2. Total data loss. All vhosts and users were gone after the update.
(In reply to comment #0) > 1. rabbitmq-server shutting down during update - as far as I know this is a > no-go? This is just how the packaging scripts work. Also you cannot do it with current "non-packaged" version either. This is not a bug in the package rather an enhancement request in the application itself. I would suggest asking on the rabbitmq mailing list first. > 2. Total data loss. All vhosts and users were gone after the update. Release notes for 2.1.0: "Upgrading ========= The database schema has changed since the last release (2.0.0). When starting, the RabbitMQ server will detect the existence of an old database and will move it to a backup location, before creating a fresh, empty database, and will log a warning. If your RabbitMQ installation contains important data then we recommend you contact support for assistance with the upgrade. "
>> 1. rabbitmq-server shutting down during update - as far as I know this is a >> no-go? > This is just how the packaging scripts work. Also you cannot do it with > current "non-packaged" version either. This is not a bug in the package > rather an enhancement request in the application itself. I would suggest > asking on the rabbitmq mailing list first. I think you're missing my point. Let's say I have working rabbitmq server. After updating it to a new release I do no longer have a working rabbitmq server because the update has stopped the server and not restarted it. That is clearly a packaging issue. > > 2. Total data loss. All vhosts and users were gone after the update. > Release notes for 2.1.0: > "Upgrading > ========= > The database schema has changed since the last release (2.0.0). When > starting, the RabbitMQ server will detect the existence of an old > database and will move it to a backup location, before creating a > fresh, empty database, and will log a warning. If your RabbitMQ > installation contains important data then we recommend you contact > support for assistance with the upgrade. > " So you're suggesting I read the release notes for each and every package update I'm installing in the future? An update like this is clearly not acceptable for a stable EL - see also: http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies
Folks, calm down. Let's think how we could resolve this issue w/o additional damage and with mutual respect. I personally welcome ver. 2.1.0 (and newly released 2.1.1) in EL-5 since it offers several bugfixes over 2.0.x. However I'm really sad because of changed DB scheme. Hubert, are there are any means to do automatic conversion from old DB to new on?
(In reply to comment #2) > >> 1. rabbitmq-server shutting down during update - as far as I know this is a > >> no-go? > > > This is just how the packaging scripts work. Also you cannot do it with > > current "non-packaged" version either. This is not a bug in the package > > rather an enhancement request in the application itself. I would suggest > > asking on the rabbitmq mailing list first. > > I think you're missing my point. > > Let's say I have working rabbitmq server. > > After updating it to a new release I do no longer have a working rabbitmq > server because the update has stopped the server and not restarted it. > > That is clearly a packaging issue. Ok, I thought you were talking about the hot code swapping since we are in the Erlang world. But anyway, stopping the server during the upgrade is nothing unusual just look at the specs of other erlang packages like ejabbberd or couchdb so rabbitmq-server is following the standard in this case. > > So you're suggesting I read the release notes for each and every package > update I'm installing in the future? > > An update like this is clearly not acceptable for a stable EL - see also: > > http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies This was explanation for your problem, and the data was not lost it was backup-ed up. > I personally welcome ver. 2.1.0 (and newly released 2.1.1) in EL-5 since it > offers several bugfixes over 2.0.x. However I'm really sad because of changed > DB scheme. As far as I remember the db format has changed between many of the releases and if we were to stay without the db scheme then many of the critical bugs wouldn't be visible in the stable EL-5 branch, which I think is less evil. > Hubert, are there are any means to do automatic conversion from old DB to new > on? Nothing I am aware of but I will talk to the rabbit team.
Not that it helps a lot now this is in updates, but for posterity, this kind of change runs counter to both the letter and intent of EPEL update policy, per http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#A_major_version_update
(In reply to comment #4) > > I personally welcome ver. 2.1.0 (and newly released 2.1.1) in EL-5 since it > > offers several bugfixes over 2.0.x. However I'm really sad because of changed > > DB scheme. > > As far as I remember the db format has changed between many of the releases and > if we were to stay without the db scheme then many of the critical bugs > wouldn't be visible in the stable EL-5 branch, which I think is less evil. > > > Hubert, are there are any means to do automatic conversion from old DB to new > > on? > > Nothing I am aware of but I will talk to the rabbit team. I talked to the rabbit team and fortunately they are actively working on that problem. So there are really high chances that 2.0.x -> 2.1.0 db schema change was the last one that affects the end users and in the next release the actual db migration will be automatic. I will leave the bug open until then.
rabbitmq-server-2.2.0-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/rabbitmq-server-2.2.0-1.el5
rabbitmq-server-2.2.0-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update rabbitmq-server'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/rabbitmq-server-2.2.0-1.el5
rabbitmq-server-2.2.0-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
Hubert, Would it be possible to also build rabbitmq-server-2.2.0 for EPEL-6? It appears to have been built only for F13, F14, F15, and EPEL-5. tia, jpo