# Logstash 2.3.2 redis input crash

**URL:** <https://discuss.elastic.co/t/logstash-2-3-2-redis-input-crash/51379>\
**Category:** Logstash\
**Created:** [May 31, 2016, 6:31am UTC](https://discuss.elastic.co/t/logstash-2-3-2-redis-input-crash/51379 "2016-05-31T06:31:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ronald\_Moesbergen](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@Ronald\_Moesbergen](https://discuss.elastic.co/u/Ronald_Moesbergen)\
**Post date:** [May 31, 2016, 6:31am UTC](https://discuss.elastic.co/t/logstash-2-3-2-redis-input-crash/51379/1 "2016-05-31T06:31:38Z")

</div>

Hi,

I've recently upgraded logstash to version 2.3.2 and notice that since this upgrade, whenever a redis error occurs, logstash crashes wit the following exception:

:exception=\>#\<Redis::CommandError: OOM command not allowed when used memory \> 'maxmemory'.\>, :backtrace=\>["/usr/local/logstash/vendor/bundle/jruby/1.9/gems/redis-3.3.0/lib/redis/client.rb:121:in `call'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/redis-3.3.0/lib/redis.rb:1070:in`rpush'",  
"/usr/local/logstash/vendor/bundle/jruby/1.9/gems/redis-3.3.0/lib/redis.rb:58:in `synchronize'", "/usr/local/logstash/vendor/jruby/lib/ruby/1.9/monitor.rb:211:in`mon\_synchronize'",  
"/usr/local/logstash/vendor/jruby/lib/ruby/1.9/monitor.rb:210:in `mon_synchronize'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/redis-3.3.0/lib/redis.rb:58:in`synchronize'",  
"/usr/local/logstash/vendor/bundle/jruby/1.9/gems/redis-3.3.0/lib/redis.rb:1069:in `rpush'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-redis-2.0.5/lib/logstash/outputs/redis.rb:246:in`send\_to\_redis'",  
"org/jruby/RubyProc.java:281:in `call'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-codec-json-2.1.4/lib/logstash/codecs/json.rb:42:in`encode'",  
"/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-redis-2.0.5/lib/logstash/outputs/redis.rb:152:in `receive'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/outputs/base.rb:83:in`multi\_receive'",  
"org/jruby/RubyArray.java:1613:in `each'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/outputs/base.rb:83:in`multi\_receive'",  
"/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/output\_delegator.rb:130:in `worker_multi_receive'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/output_delegator.rb:129:in`worker\_multi\_receive'",  
"/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/output\_delegator.rb:114:in `multi_receive'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/pipeline.rb:301:in`output\_batch'",  
"org/jruby/RubyHash.java:1342:in `each'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/pipeline.rb:301:in`output\_batch'",  
"/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/pipeline.rb:232:in `worker_loop'", "/usr/local/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/pipeline.rb:201:in`start\_workers'"

Looks like a bug?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 31, 2016, 6:39am UTC](https://discuss.elastic.co/t/logstash-2-3-2-redis-input-crash/51379/2 "2016-05-31T06:39:15Z")

</div>

What version of redis?

---

<div class="post-metadata">

**Author:** ![Ronald\_Moesbergen](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@Ronald\_Moesbergen](https://discuss.elastic.co/u/Ronald_Moesbergen)\
**Post date:** [May 31, 2016, 6:51am UTC](https://discuss.elastic.co/t/logstash-2-3-2-redis-input-crash/51379/3 "2016-05-31T06:51:18Z")

</div>

Redis 3.0.7.

---

<div class="post-metadata">

**Author:** ![Ronald\_Moesbergen](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@Ronald\_Moesbergen](https://discuss.elastic.co/u/Ronald_Moesbergen)\
**Post date:** [May 31, 2016, 6:59am UTC](https://discuss.elastic.co/t/logstash-2-3-2-redis-input-crash/51379/4 "2016-05-31T06:59:09Z")

</div>

Hmm, I just noticed this:

[422170.826951] Out of memory: Kill process 1404 (java) score 242 or sacrifice child  
[422170.827468] Killed process 1404, UID 498, (java) total-vm:10827908kB, anon-rss:1431992kB, file-rss:5548kB

So it seems redis caused the machine to go OOM and the kernel chose to kill logstash instead... Never mind, not a logstash issue. 🙂

---

<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:55am UTC](https://discuss.elastic.co/t/logstash-2-3-2-redis-input-crash/51379/5 "2017-07-06T04:55:23Z")

</div>