We should revisit if this is still an issue with the Focal version of
RabbitMQ.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783203
Title:
Upgrade to RabbitMQ 3.6.10 causes beam lockup in
** Changed in: erlang (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783203
Title:
Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
To
Triaged the charm task until we can validate the fixes against the
erlang/rabbit bits
** Changed in: charm-rabbitmq-server
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
raising erlang bug task; I think we need to address the two ERL-* issues
in the xenial erlang version as identified in #13.
** Also affects: erlang (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I mostly failed to explain the impact of the above Erlang bugs.
Due to ERl-430 and ERL-448 above, nodes that had any TCP connections
open (possibly from HTTP requests) could fail to stop (shut down),
accept new TCP connections (including from HTTP clients, RabbitMQ CLI
tools) and respond on
There isn't a whole lot of details about node state here but GM (a
multicast module) has nothing to do with the management plugin.
According to the above comments this is on Erlang 18.3 which has known
bugs that stop any activity on a node that had accepted any TCP
connections (including HTTP
>From the commit message https://github.com/rabbitmq/rabbitmq-
server/pull/1431 "Avoid infinite loop when dropping entries in the GM"
in 3.6.15 sounds interesting, as we do seem to see some kind of infinite
loop here. I don't have an explanation though as to why GM would be
interacting with the
The latest release in the 3.6.x series seems to be 3.6.16. Almost all
releases since 3.6.10 list changes to the management plugin, but I
didn't spot anything obvious. Here are the release notes for each:
https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_16
The latest release in the 3.6.x series seems to be 3.6.16. Almost all
releases since 3.6.10 list changes to the management plugin, but I
didn't spot anything obvious. Here are the release notes for each:
https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_16
Forgot to mention: The log in /var/log/rabbitmq/rab...@hostname.log just
stops when the server hangs, no output until after it is being
restarted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783203
We are also seeing this issue after upgrading OpenStack from Pike to
Queens. It only seems to affect our larger setups, it wasn't seen during
testing on our staging setup. The good thing is that I can confirm that
disabling the management plugin seems to avoid the issue. We also have a
core dump,
for people being hit by this bug, it would be helpful if you could
generate a core file while rabbit is still stuck, this may give us some
insights of where the process is looping.
$ sudo gcore -o lp1783203.core $PID
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783203
Title:
Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
To manage notifications about this bug go to:
Now that is a useful nugget of information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783203
Title:
Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
To manage
Now that is a useful nugget of information.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1783203
Title:
Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
Adding that the config "management_plugin=true" causes the crashing to
happen with the web.yaml stack, while having it false does not cause the
crashing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783203
17 matches
Mail list logo
