group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #48303
[Bug 1890846] Re: [plugin][rabbitmq] add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
Already in bionic, as it's in 4.1, and bionic is on 4.4
** Changed in: sosreport (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1890846
Title:
[plugin][rabbitmq] add output of: rabbitmqctl eval
'rabbit_diagnostics:maybe_stuck().'
Status in sosreport package in Ubuntu:
Fix Released
Status in sosreport source package in Xenial:
New
Status in sosreport source package in Bionic:
Fix Released
Status in sosreport source package in Focal:
Fix Released
Status in sosreport source package in Groovy:
Fix Released
Bug description:
[Impact]
We have seen customer cases where the output of
`rabbit_diagnostics:maybe_stuck()` provided helpful information in
debugging the root cause. Automatically collecting this information
will potentially expedite the debugging of rabbitmq-server related
issues.
[Test Case]
Run the rabbitmq plugin on a machine running a rabbitmq broker. On a
fresh Focal install, the output will look like the following:
2020-09-18 12:55:47 There are 257 processes.
2020-09-18 12:55:47 Investigated 1 processes this round, 5000ms to go.
2020-09-18 12:55:47 Investigated 1 processes this round, 4500ms to go.
2020-09-18 12:55:48 Investigated 1 processes this round, 4000ms to go.
2020-09-18 12:55:48 Investigated 1 processes this round, 3500ms to go.
2020-09-18 12:55:49 Investigated 1 processes this round, 3000ms to go.
2020-09-18 12:55:49 Investigated 1 processes this round, 2500ms to go.
2020-09-18 12:55:50 Investigated 1 processes this round, 2000ms to go.
2020-09-18 12:55:50 Investigated 1 processes this round, 1500ms to go.
2020-09-18 12:55:51 Investigated 1 processes this round, 1000ms to go.
2020-09-18 12:55:51 Investigated 1 processes this round, 500ms to go.
2020-09-18 12:55:52 Found 1 suspicious processes.
2020-09-18 12:55:52 [{pid,<10643.1.0>},
{registered_name,erts_code_purger},
{current_stacktrace,
[{erts_code_purger,wait_for_request,0,[]}]},
{initial_call,{erts_code_purger,start,0}},
{message_queue_len,0},
{links,[]},
{monitors,[]},
{monitored_by,[]},
{heap_size,1598}]
ok
In case some Erlang runtime threads are stuck they will show in the
above list.
[Regression Potential]
This function was introduced with rabbitmq-server-3.3.4 which covers
Xenial upwards. The command would not work on earlier versions of
rabbitmq-server.
[Other Info]
* Upstream commits:
https://github.com/sosreport/sos/commit/af5891786ff8c4e33c341fe9cca690fc77ac768f
https://github.com/sosreport/sos/commit/5b5ebe2d2c9d579931c8d6a78101e16d6abfa527
[Original Description]
Extend the rabbitmq plugin to include the output of:
sudo rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
This information is useful to get insights of the state of the erlang
virtual machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1890846/+subscriptions