Downgrade rabbitmq-server from version 3.8.9 to 3.7.11 #2735
-
|
I want to downgrade the rabbitmq-server to a specific version and also the erlang cause the classic format of config is not supported in the newer version of rabbitmq-server. I'm looking for a solution for Ubuntu 18 version. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
|
@anandtripathi5 RabbitMQ does not support in place downgrades. There are internal data store migrations, message store or Raft log format changes, and other kind of changes that are irreversible. You can use the Blue/Green deployment strategy to move from one cluster to another. However, I strongly believe that it would be wrong for you to downgrade. First of all, the classic config format is absolutely supported by 3.8, from an additional Another reason why this is a bad idea is that RabbitMQ 3.7 is entirely out of support. We will not produce any more 3.7 releases, including for serious issues and security issues. Needless to say you will be missing our one several major new features only available in the |
Beta Was this translation helpful? Give feedback.
-
|
I'm curious as to why you want to downgrade to v3.7.11 @anandtripathi5? |
Beta Was this translation helpful? Give feedback.
-
|
According to the original question, "cause the classic format of config is not supported in the newer version of rabbitmq-server" (which is not correct as I explained above) |
Beta Was this translation helpful? Give feedback.
-
|
Is that the reason @anandtripathi5? |
Beta Was this translation helpful? Give feedback.
-
|
Actually, recently we stuck into an error "certify received CLIENT ALERT: Fatal - Unknown CA". We are using 5671 port and amqps protocol. The configuration was fine and everything was working fine. But suddenly it stopped yesterday and this error was coming continuously. Now we have used 5672 port(without SSL) and meanwhile just debugging why it failed for SSL. In the meantime, I thought maybe version 3.8.9 is giving error cause on our prod environments everything is working fine on 3.7.11 that's why I initiated this discussion. But I guess we can close this cause the version is nothing to do with my current problem. Thanks @michaelklishin for the quick reply. |
Beta Was this translation helpful? Give feedback.
-
|
"Unknown CA" is explicitly mentioned in the TLS guide's section on peer verification. It is absolutely not version- or configuration format-specific. Your client certificate is ultimately signed by a CA that's not trusted by the RabbitMQ node it has connected to. |
Beta Was this translation helpful? Give feedback.
@anandtripathi5 RabbitMQ does not support in place downgrades. There are internal data store migrations, message store or Raft log format changes, and other kind of changes that are irreversible. You can use the Blue/Green deployment strategy to move from one cluster to another.
However, I strongly believe that it would be wrong for you to downgrade. First of all, the classic config format is absolutely supported by 3.8, from an additional
advanced.configfile to accompany the mainrabbitmq.confto the good oldrabbitmq.configin the classic Erlang term config format. In fact,rabbitmq.confis validated and then translated to the Erlang term format under the hood, so removing support for …