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 requests) [1][2]. They were reported by team RabbitMQ in mid-2017 and fixed shortly after. Erlang 19.3.6.4 is the minimum supported version for RabbitMQ 3.6.16 primarily because of those issues. Somewhat related: RabbitMQ 3.6.x is out of support [3][4] and since January 2018 [4], Erlang 19.3.6.4 is the minimum supported version even for 3.6.x. 1. https://bugs.erlang.org/browse/ERL-430 2. https://bugs.erlang.org/browse/ERL-448 3. https://www.rabbitmq.com/which-erlang.html#old-timers 4. http://www.rabbitmq.com/changelog.html -- 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: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1783203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
