# \[RESOLVED\] Input plugin Rabbitmq

**URL:** <https://discuss.elastic.co/t/resolved-input-plugin-rabbitmq/60591>\
**Category:** Logstash\
**Created:** [September 15, 2016, 9:26am UTC](https://discuss.elastic.co/t/resolved-input-plugin-rabbitmq/60591 "2016-09-15T09:26:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![axelfelix](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@axelfelix](https://discuss.elastic.co/u/axelfelix)\
**Post date:** [September 15, 2016, 9:26am UTC](https://discuss.elastic.co/t/resolved-input-plugin-rabbitmq/60591/1 "2016-09-15T09:26:05Z")

</div>

Hi all,

I have a rabbitmq for queueing. I can see my logs comming in rabbitmq but never go out to my logstash.

**Logstash log:**

`{:timestamp=>"2016-09-15T11:10:35.118000+0200", :message=>"Queue subscription ended! Will retry in 5s", :config=>{"host"=>"127.0.0.1", "user"=>"admin", "password"=><password>, "queue"=>"test", "exchange"=>"my_exchange", "codec"=><LogStash::Codecs::Plain charset=>"UTF-8">, "debug"=>false, "add_field"=>{}, "threads"=>1, "port"=>5672, "vhost"=>"/", "ssl"=>false, "verify_ssl"=>false, "automatic_recovery"=>true, "connect_retry_interval"=>1, "passive"=>false, "arguments"=>{}, "durable"=>false, "auto_delete"=>false, "exclusive"=>false, "prefetch_count"=>256, "ack"=>true, "key"=>"logstash", "subscription_retry_interval_seconds"=>5}, :level=>:warn}`

It is working with "fanout" exchange type but not with "direct" exchange type.

Do you have any idea regarding this ?

Thanks in advance,  
Alex

---

<div class="post-metadata">

**Author:** ![vandamo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vandamo/32/8203_2.png) [@vandamo](https://discuss.elastic.co/u/vandamo)\
**Post date:** [September 15, 2016, 9:34am UTC](https://discuss.elastic.co/t/resolved-input-plugin-rabbitmq/60591/2 "2016-09-15T09:34:08Z")

</div>

> [@axelfelix](#):
>
> It is working with "fanout" exchange type but not with "direct" exchange type.

If you leave the passive flag to true (default), it means logstash rabbitmq plugin would create the missing elements (queue, binding, ...) in rabbitmq if needed, and will compare your configuration with the existing one. So probably easier to set it to false and start from an existing complete config in rabbitMQ.

Otherwise, I see you didn't reference a routing-key, which is required for a direct exchange binding to a queue.

---

<div class="post-metadata">

**Author:** ![axelfelix](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@axelfelix](https://discuss.elastic.co/u/axelfelix)\
**Post date:** [September 15, 2016, 1:39pm UTC](https://discuss.elastic.co/t/resolved-input-plugin-rabbitmq/60591/3 "2016-09-15T13:39:31Z")

</div>

Thanks for your answer, it is working now.

Have a good day.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:38am UTC](https://discuss.elastic.co/t/resolved-input-plugin-rabbitmq/60591/4 "2017-07-06T04:38:16Z")

</div>