An internal queue is locked for some reason. Try to delete it with: rabbitmqctl eval 'rabbit_amqqueue:internal_delete({resource,<<"/">>,queue,<<" versioned_notifications.info">>}).' - Gabriele Santomaggio Il giorno gio 12 set 2019 alle ore 15:37 Ben Nemec <openstack@nemebean.com> ha scritto:
Have you checked that your notification queues aren't filling up? It can cause performance problems in Rabbit if nothing is clearing out those queues.
On 9/12/19 4:35 AM, Md. Farhad Hasan Khan wrote:
Hi,
I’m getting this error continuously in rabbitmq log. Though all operation going normal, but slow. Sometimes taking long time to perform operation. Please help me to solve this.
rabbitmq version: rabbitmq_server-3.6.16
=ERROR REPORT==== 12-Sep-2019::13:04:55 ===
Channel error on connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672, vhost: '/', user: 'openstack'), channel 1:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'versioned_notifications.info' in vhost '/' due to timeout
=WARNING REPORT==== 12-Sep-2019::13:04:55 ===
closing AMQP connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672 - nova-compute:3493037:e6757c9b-1cdc-43cd-bfd3-dcb58aa4974a, vhost: '/', user: 'openstack'):
client unexpectedly closed TCP connection
Thanks & B’Rgds,
Rony
-- Gabriele Santomaggio