# Logstash shipper events stuck at redis

**URL:** <https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694>\
**Category:** Logstash\
**Created:** [February 2, 2016, 6:38am UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694 "2016-02-02T06:38:57Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kishore](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@Kishore](https://discuss.elastic.co/u/Kishore)\
**Post date:** [February 2, 2016, 6:38am UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694/1 "2016-02-02T06:38:57Z")

</div>

Kindly verify my redis input configuration for logstash indexer, below is the input config details which worked for some time later it is not working.  
I have upgraded to logstash 2.1.1 from logstash 1.4.2

input{ redis { host =\> "host" port =\> "7000" data\_type =\> "list" key =\> "syslog" } }

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 2, 2016, 7:08am UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694/2 "2016-02-02T07:08:00Z")

</div>

Well, what happens? Is there an error or warning message in the logs? Do you get additional clues if you crank up the log level with `--verbose` or `--debug`?

---

<div class="post-metadata">

**Author:** ![Kishore](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@Kishore](https://discuss.elastic.co/u/Kishore)\
**Post date:** [February 2, 2016, 7:18am UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694/3 "2016-02-02T07:18:13Z")

</div>

I couldn't find any log level in the settings, could you please tell me how to find current logging level

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 2, 2016, 7:31am UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694/4 "2016-02-02T07:31:31Z")

</div>

The log level is set via command-line options, listed above. Without those options you get the default log level.

---

<div class="post-metadata">

**Author:** ![Kishore](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@Kishore](https://discuss.elastic.co/u/Kishore)\
**Post date:** [February 2, 2016, 9:48am UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694/5 "2016-02-02T09:48:02Z")

</div>

I am getting below message when i use --verbose.

Flushing buffer at interval {:instance=\>"LogStash::Outputs::ElasticSearch::Buffer:0x7b452a3e operations\_mutex=Mutex:0x7582db26\>, max\_size=500, operations\_lock=Java::JavaUtilConcurrentLocks::ReentrantLock:0x71bd414e\>, submit\_proc=Proc:0x66f9096e/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.2.0-java/lib/logstash/outputs/elasticsearch/common.rb:55\>, logger=#\<Cabin::Channel:0x541a57c metrics=Cabin::Metrics:0x1eed23ab metrics\_lock=#Mutex:0x54902e52\>, metrics={}, channel=Cabin::Channel:0x541a57c ...\>\>, subscriber\_lock=Mutex:0x7a0cefd7\>, level=:info, subscribers={12590=\>Cabin::Outputs::IO:0x5e94a32 io=\<IO:fd 1\>, lock=Mutex:0x50de1663\>}, @data={}\>, last\_flush=2016-02-02 04:07:35 -0500, @flush\_interval=1, stopping=#Concurrent::AtomicBoolean:0x4db129f8\>, buffer=[], flush\_thread=Thread:0x49a69456 run\>\>", :interval=\>1, :level=\>:info}

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 2, 2016, 6:54pm UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694/6 "2016-02-02T18:54:43Z")

</div>

Surely that's not the only thing you get with verbose logging. Anything in there that hints at a problem?

---

<div class="post-metadata">

**Author:** ![Kishore](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@Kishore](https://discuss.elastic.co/u/Kishore)\
**Post date:** [February 3, 2016, 6:38am UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694/7 "2016-02-03T06:38:49Z")

</div>

Apart from above message, getting redis warning.

Redis connection problem {:exception=\>#Redis::CommandError: CROSSSLOT Keys in request don't hash to the same slot\>, :level=\>:warn}

---

<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, 5:13am UTC](https://discuss.elastic.co/t/logstash-shipper-events-stuck-at-redis/40694/8 "2017-07-06T05:13:18Z")

</div>