Queue Ghost consumers

[Shweta Lokhande]

Hi,

Hope you are doing great.

I need your assistance in the below situation.

In the test environment, there are rabbit consumers connected to the RELAY-* queues even when the app is stopped. This is causing messages to the queues being consumed by these “ghost” consumers, and the actual application receiving no data unless the application’s consumer happens to pick it up first.

 

For example, rabbitTST queue “RELAY-TASK-PUBLISH-QUESTION-STORE” RELAY (grails app) should be the only consumer, it is shut down at the moment on the server and yet there are currently 14 consumers… 

Not a rabbit/queue/consumer expert but I don’t think that is how its supposed to work. 

Please provide some measures.

Thank you.

Regards,

Shweta 

[Michael Klishin]

What RabbitMQ version is used? How are those "ghost" consumers observed? How was the app stopped?

What's in server logs?

Have you verified that the server logs that a client connection was closed or lost? Have you tried

using a lower (but not too low) heartbeat timeout? [1].

Please give us something to work with.

1. http://www.rabbitmq.com/heartbeats.html

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Shweta Lokhande]

Hi Michael,

Version :  RabbitMQ 3.3.5, Erlang R14B04

 I could see ghost consumers on management plugin. There should only be 2 consumers but current status keeps changing.Sometimes it is 14 consumers , sometimes 10, likewise. 

App was running on a tomcat instance. When stopped the app is shutdown on that instance.

Server logs show this 

"

=ERROR REPORT==== 5-Oct-2017::17:04:14 ===

error on AMQP connection <0.13009.515>:

{ssl_upgrade_error,ekeyfile}

=INFO REPORT==== 5-Oct-2017::17:04:14 ===

accepting AMQP connection <0.13019.515> (10.142.33.2:22343 -> 10.142.18.21:5671)

=ERROR REPORT==== 5-Oct-2017::17:04:14 ===

SSL: 1112: error:[] /etc/rabbitmq/ssl/rabbitmq_wildcard.key

  [{ssl_connection,init_private_key,5},

   {ssl_connection,ssl_init,2},

   {ssl_connection,init,1},

   {gen_fsm,init_it,6},

   {proc_lib,init_p_do_apply,3}]  

 

"

Cert looks good, 

" Validity

            Not Before: Jul 20 14:32:50 2016 GMT

            Not After : Jan 18 14:32:50 2038 GMT"

Please suggest.

Thanks in advance.

Regards,

Shweta 

[Michael Klishin]

I'm afraid the only piece of advice we have for 3.3.5 is "please upgrade".

It is 26 releases and more than 3 years behind.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Shweta Lokhande]

Hi Michael,

Certainly, we have new Rabbit servers which are not live yet. It will take around 1 or 2 months to get approvals from higher management. Hope you understand.

The application testing is to be done using old rabbit servers as this has to be completed by tomorrow. 

Hence, this is not a feasible option to even ponder over using the upgraded rabbit version.

Can you please suggest for this problem as we have  Rabbit 3.3.5 version currently up and running.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michael Klishin]

See what `rabbitmqctl list_consumers` returns. It is the source of truth, not the management UI (which stores periodically

emitted stats). It can be an issue that has been long fixed, see [1].

See [3] for how to reset the stats database in versions earlier than 3.6.7.

That's about as much as we can suggest for 3.3.x. Please communicate it to your management that running a 3+ year old,

26 releases out of date version is not an optimal strategy in terms of getting help or obtaining support.

1. http://www.rabbitmq.com/changelog.html

2. http://previous.rabbitmq.com/v3_5_7/management.html

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.