'unknown' consumers in queues

[sfesfizh]

Hi! Using cluster with 4 hosts of 3.6.3 version and in some of queues I see 'unknown' consumers with information about deleted or not existed object. CLI information (sudo rabbitmqctl list_consumers -p /) does not show any of 'unknown' consumers and also no in 'channels'

[michaelklishin]

Stats DB intentionally drops events when it cannot keep up: that's one possible reason for what you see. rabbitmqctl list_consumers takes a "snapshot" and is not event-driven.

You can reset stats DB as explained in the docs. There is no solution to this with the current design, although future versions should make it less likely. Channels that no longer exist will be cleaned up eventually by the plugin.

Can you post your logs to rabbitmq-users, please?

[sfesfizh]

Sorry, my logs in /var/log/rabbitmq are empty now (empty file)... I should increase log level and check some

[michaelklishin]

If both regular and SASL logs are empty and weren't deleted
or rotated, then chances are there were no exceptions to inspect.

Please watch #236,
some stats
aggregation changes there should make this a lot less likely
("pre-aggregation" will happen
on nodes themselves).

On Tue, Jul 19, 2016 at 12:34 PM, Oleksandr notifications@github.com
wrote:

Sorry, my logs in /var/log/rabbitmq are empty now (empty file)... I should
increase log level and check some

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#254 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAEQqTaqUs84PGtB5hNfTw4EuE4aANNks5qXJoOgaJpZM4JPiIY
.

MK

Staff Software Engineer, Pivotal/RabbitMQ

[sfesfizh]

Some rotated logs exists but about a month ago. I made updates and reconfigurations later.
I will increase log level and check

[michaelklishin]

We are primarily after SASL logs and those are not controlled by log verbosity levels. Also, there is no "debug" level in 3.6.x either.

[sfesfizh]

So why my logs are empty?

[michaelklishin]

We cannot know. Reasons range from "they were rotated very recently" to
"they were removed" to "SASL log only contains
unhandled exceptions and there were none" to "you are looking at the wrong
file".

On Tue, Jul 19, 2016 at 12:41 PM, Oleksandr notifications@github.com
wrote:

So why my logs are empty?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#254 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAEQpVz-qIarZmRWF7hZDsvQF7w5v27ks5qXJvTgaJpZM4JPiIY
.

MK

Staff Software Engineer, Pivotal/RabbitMQ

[sfesfizh]

[sfesfizh]

Resetting of stats DB didn't help

[michaelklishin]

@sfesfizh either you haven't reset it properly or the consumers are not phantom. All of the management plugin data is kept in memory.

This is long overdue for moving to rabbitmq-users.

[sfesfizh]

Resetted with this command:

rabbitmqctl eval 'supervisor2:terminate_child(rabbit_mgmt_sup_sup, rabbit_mgmt_sup), rabbit_mgmt_sup_sup:start_child().'

Also it can't be real consumers...

P.S. Helped with service restart one-by-one with systemctl restart

[michaelklishin]

Everything collected in the management database is there because there was
an event
that triggered it: a consumer was added (or cancelled), a connection opened
(or closed), etc.
All of that data is stored entirely in RAM. So yes, those were real
consumers at some point.

Are you sure you run the terminate_child function on the node that hosts
the stats DB?

Again, please take this to the mailing list. Our team does not use GitHub
issues for questions
or support.

On Tue, Jul 19, 2016 at 4:16 PM, Oleksandr notifications@github.com wrote:

Resetted with this command:

rabbitmqctl eval 'supervisor2:terminate_child(rabbit_mgmt_sup_sup,
rabbit_mgmt_sup),
rabbit_mgmt_sup_sup:start_child().'

Also it can't be real consumers...

P.S. Helped with service restart one-by-one with systemctl restart

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#254 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAEQvMIjtiYld1P3piXbI4G0rlnNaWhks5qXM4agaJpZM4JPiIY
.

MK

Staff Software Engineer, Pivotal/RabbitMQ