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
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
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
Hi Gabriele, This is the output. “versioned_notifications.error ”. so please help me to solve this. [root@controller1 ~]# rabbitmqctl list_queues name consumers messages | grep notifications notifications.debug 3 0 notifications.critical 3 0 notifications.error 3 0 notifications.info 3 0 notifications.warn 3 0 notifications.audit 3 0 notifications.sample 3 0 versioned_notifications.error 0 14 [root@controller1 ~]# Thanks & B’Rgds, Rony From: Gabriele Santomaggio [mailto:g.santomaggio@gmail.com] Sent: Monday, September 16, 2019 11:37 PM To: Ben Nemec Cc: rony.khan@brilliant.com.bd; OpenStack Discuss Subject: Re: Rabbitmq error report An internal queue is locked for some reason. Try to delete it with: rabbitmqctl eval 'rabbit_amqqueue:internal_delete({resource,<<"/">>,queue,<<"versioned_notifications.info <http://versioned_notifications.info> ">>}).' - Gabriele Santomaggio Il giorno gio 12 set 2019 alle ore 15:37 Ben Nemec <openstack@nemebean.com <mailto: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 <http://192.168.21.56:60116> -> 192.168.21.11:5672 <http://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 <http://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 <http://192.168.21.56:60116> -> 192.168.21.11:5672 <http://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
Rony, Sorry but I am not understanding. The error you have is:
operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'versioned_notifications.info' in vhost '/' due to timeout
so you need to remove the queue called: versioned_notifications.info using: ``` rabbitmqctl eval 'rabbit_amqqueue:internal_delete({resource,<<"/">>,queue,<<" versioned_notifications.info">>}).' ```
This is the output. “versioned_notifications.error ”. so please help me to solve this.
"versioned_notifications.error" is another queue. Cheers - Gabriele Santomaggio Il giorno mar 17 set 2019 alle ore 08:11 Md. Farhad Hasan Khan < rony.khan@brilliant.com.bd> ha scritto:
Hi Gabriele,
This is the output. “versioned_notifications.error ”. so please help me to solve this.
[root@controller1 ~]# rabbitmqctl list_queues name consumers messages | grep notifications
notifications.debug 3 0
notifications.critical 3 0
notifications.error 3 0
notifications.info 3 0
notifications.warn 3 0
notifications.audit 3 0
notifications.sample 3 0
versioned_notifications.error 0 14
[root@controller1 ~]#
Thanks & B’Rgds,
Rony
*From:* Gabriele Santomaggio [mailto:g.santomaggio@gmail.com] *Sent:* Monday, September 16, 2019 11:37 PM *To:* Ben Nemec *Cc:* rony.khan@brilliant.com.bd; OpenStack Discuss *Subject:* Re: Rabbitmq error report
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
-- Gabriele Santomaggio
participants (3)
-
Ben Nemec
-
Gabriele Santomaggio
-
Md. Farhad Hasan Khan