operation queue.bind caused a channel exception not_found

[mike....@deepcrawl.com]

version rabbitmq-server                  3.6.1-1

HA cluster 2 nodes

=ERROR REPORT==== 24-Jun-2016::14:28:09 ===

Channel error on connection <0.10663.9> (10.0.15.226:57264 -> 10.0.15.251:5672, vhost: 'staging', user: 'staging'), channel 1:

operation queue.bind caused a channel exception not_found: "no binding ha.queue.transformer between exchange 'ha.queue.transformer' in vhost 'staging' and queue 'ha.queue.transformer' in vhost 'staging'"

Running into this error but cannot work out how to fix it?

I have tried deleting the queue but still running into it :(

[Michael Klishin]

The error here is probably not really correct: RabbitMQ cannot (re)-create a binding

but reports it as if it didn't exist.

Can you post the SASL log? Have you tried re-declaring both the exchange and the queue? What are their properties (durability, etc)?

You can use different names as a workaround, by the way.

--
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-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[mike....@deepcrawl.com]

Here is the only entry n the sasl log althought its repeated a fair bt

=SUPERVISOR REPORT==== 24-Jun-2016::15:34:16 ===

     Supervisor: {<0.25900.12>,rabbit_channel_sup_sup}

     Context:    shutdown_error

     Reason:     shutdown

     Offender:   [{nb_children,1},

                  {name,channel_sup},

                  {mfargs,{rabbit_channel_sup,start_link,[]}},

                  {restart_type,temporary},

                  {shutdown,infinity},

                  {child_type,supervisor}]

I have tried redeclaring the queue but not the exchange

[Michael Klishin]

unfortunately that does not clarify what’s going on :(

On 24 June 2016 at 19:00:32, mike....@deepcrawl.com (mike....@deepcrawl.com) wrote:
> Here is the only entry n the sasl log althought its repeated a fair bt
>
> =SUPERVISOR REPORT==== 24-Jun-2016::15:34:16 ===
> Supervisor: {<0.25900.12>,rabbit_channel_sup_sup}
> Context: shutdown_error
> Reason: shutdown
> Offender: [{nb_children,1},
> {name,channel_sup},
> {mfargs,{rabbit_channel_sup,start_link,[]}},
> {restart_type,temporary},
> {shutdown,infinity},
> {child_type,supervisor}]
>
> I have tried redeclaring the queue but not the exchange
>
> On Friday, June 24, 2016 at 4:40:31 PM UTC+1, Michael Klishin wrote:
> >
> > The error here is probably not really correct: RabbitMQ cannot (re)-create
> > a binding
> > but reports it as if it didn't exist.
> >
> > Can you post the SASL log? Have you tried re-declaring both the exchange
> > and the queue? What are their properties (durability, etc)?
> >
> > You can use different names as a workaround, by the way.
> >
> > On Fri, Jun 24, 2016 at 5:37 PM, >

> To post to this group, send an email to rabbitm...@googlegroups.com.

[mike....@deepcrawl.com]

Couldn't work it out so had to blow it all away and start again just to get the system up and running

[Ankur Deep Jaiswal]

happens to me all the time, i haven't figured out why. i just rename the queue and then it starts working

[Michael Klishin]

Hi Ankur,

If you have a way to reproduce this, can you please do a traffic capture on all RabbitMQ nodes

with tcpdump while running it and send us the results off list?

A workload that can reproduce this would be extremely appreciated as well as we currently don't

have a way of reproducing this.

Thank you.

--

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.

[Ankur Deep Jaiswal]

Hi Micheal,

This is my rabbitmq.config

[

  {rabbit,

    [

      {log_levels, [{connection, debug}, {channel, debug}]}

    ]

  }

].

i am attaching the file with both scenarios that are working and not working.

On Friday, June 24, 2016 at 8:07:11 PM UTC+5:30, mike....@deepcrawl.com wrote:

[Michael Klishin]

Thank you.

Can you reproduce it with 3.6.10 and post the same captures?

Our team is quite busy on a number of fronts but we'd like to get to the bottom of this

and a couple of similarly looking issues for 3.6.12 or so.

--

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.

[Ankur Deep Jaiswal]

Hi Michael,

this is running on rabbitmq 3.6.10

[{pid,20415},

 {running_applications,

     [{rabbitmq_tracing,"RabbitMQ message logging / tracing","3.6.10"},

      {rabbitmq_management,"RabbitMQ Management Console","3.6.10"},

      {rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.6.10"},

      {cowboy,"Small, fast, modular HTTP server.","1.0.4"},

      {cowlib,"Support library for manipulating Web protocols.","1.0.2"},

      {rabbitmq_management_agent,"RabbitMQ Management Agent","3.6.10"},

      {rabbit,"RabbitMQ","3.6.10"},

      {os_mon,"CPO  CXC 138 46","2.2.14"},

      {amqp_client,"RabbitMQ AMQP Client","3.6.10"},

      {rabbit_common,

          "Modules shared by rabbitmq-server and rabbitmq-erlang-client",

          "3.6.10"},

      {inets,"INETS  CXC 138 49","5.9.7"},

      {ranch,"Socket acceptor pool for TCP protocols.","1.3.0"},

      {compiler,"ERTS  CXC 138 10","4.9.4"},

      {syntax_tools,"Syntax tools","1.6.12"},

      {ssl,"Erlang/OTP SSL application","5.3.2"},

      {public_key,"Public key infrastructure","0.21"},

      {asn1,"The Erlang ASN1 compiler version 2.0.4","2.0.4"},

      {crypto,"CRYPTO version 2","3.2"},

      {xmerl,"XML parser","1.3.5"},

      {mnesia,"MNESIA  CXC 138 12","4.11"},

      {sasl,"SASL  CXC 138 11","2.3.4"},

      {stdlib,"ERTS  CXC 138 10","1.19.4"},

      {kernel,"ERTS  CXC 138 10","2.16.4"}]},

 {os,{unix,linux}},

 {erlang_version,

     "Erlang R16B03 (erts-5.10.4) [source] [64-bit] [async-threads:64] [kernel-poll:true]\n"},

On Friday, June 24, 2016 at 8:07:11 PM UTC+5:30, mike....@deepcrawl.com wrote:

[Michael Klishin]

OK, thanks. We will get to it after 3.6.11 is out with Erlang/OTP 20 compatibility.

--

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.

[Ankur Deep Jaiswal]

Hi Micheal,

sorry to bug you, but can you let me know when to expect updates on this issue.

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]

An umbrella GitHub issue for similar scenarios with some findings, a discovered synthetic way to reproduce

and PRs merged for 3.7.13 that hopefully address at least some scenarios (we don't have enough evidence and understanding

to claim that every case is addressed): https://github.com/rabbitmq/rabbitmq-server/issues/1873.

--

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-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]

We produced an rc.2 a few hours ago. 3.7.13 GA is now expected early next week.

We don't have any pending changes for 3.7.13.

Please give it a try :) [1]

1. https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.7.13-rc.2