3.3 to 3.8 upgrade path Centos 7

[Karl Volz]

Hello -

The OEL7 system I am upgrading has what I believe are the latest OS distributed versions of rabbitmq-server (3.3.5) and erlang (erlang-R16B-03.18.el7.x86_64).

Our test upgrade of  erlang to erlang-23.3.4.1 and rabbitmq to 3.8.17 via yum install of the erlang minimal rpm and rabbitrpm package from github was not really successful. Although the packages did install, the upgrade of rabbit data fails. 

The documentation suggests an upgrade from 3.3 to 3.8 is not possible without an intermediate upgrade to 3.6. Is there additional documentation for a path forward for our system that will allow us to keep our data viable after the upgrade? In particular where might I find a 3.6 rpm for the intermediate upgrade? Perhaps I misunderstand the issue and someone can suggest a better upgrade path.

Thanks,

Karl

[Karl Volz]

I think I found my answer. I just did not look in the right place for the package. 

[Arvind Tk]

Hi, Either way an upgrade is still a full uninstall of 3.3 followed by a fresh install of 3.8 I believe.

Is the direct upgrade to 3.8 not possible because the node can't do the required migrations (DB etc) from 3.3 ?

Regards

[Karl Volz]

Yes the migrations/updates of the data appear to fail. 

Karl

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/dd2f86c1-1d8d-40eb-91a8-de01908664a9n%40googlegroups.com.

[Karl Volz]

The OS is OEL 7.  I need to use the compatibilty matric to determine the max version of supported erlang (20.3) for rabbit 3.6. Then upgrade both erlang and rabbit incrementally to target version of erlang (23) and rabbitmq (3.8).The method I used was:

1.  download the old and target versions of erlang and rabbitmq from github with wget
2. stop rabbitmq-server via "systemctl stop rabbitmq-server" and confirm epmd not running
3. remove erlang, erlang-erts, rabbitmq and all dependencies via yum
4. Install erlang-20.3 and rabbitmq-3.6.16 rpms with yum
5. start rabbit via "systemctl start rabbitmq-server"
6. stop rabbitmq-server via "systemctl stop rabbitmq-server" and confirm epmd not running
7. Install/upgrade erlang-23 and rabbitmq-server-3.8 rpms with yum
8. start rabbit via "systemctl start rabbitmq-server" with no rabbitmq.conf
9. add rabbitmq.conf with our required port setting 
10. restart rabbitmq-server

In /var/log/rabbitmq/rabbit@mysteryhost_upgrade.log I do see some errors of type:

Queue index directory '/var/lib/rabbitmq/mnesia/rabbit@mystery-host/queues/8X5081QYXIEHBZRI5X2T453B3' not found for queue 'something local.content.job.ACMPicklistRemoveJob' in vhost '/'

But the log also posts a bunch of these:

2021-06-11 11:59:36.322 [info] <0.754.0> Finished migrating queue com.vendor.blah.queue.recalc.disposition in vhost /

And the service starts.

I have some checks to do I guess.