# Logstash 2.3 redis input not compatible with redis 2.4.10

**URL:** <https://discuss.elastic.co/t/logstash-2-3-redis-input-not-compatible-with-redis-2-4-10/46278>\
**Category:** Logstash\
**Created:** [April 4, 2016, 6:13pm UTC](https://discuss.elastic.co/t/logstash-2-3-redis-input-not-compatible-with-redis-2-4-10/46278 "2016-04-04T18:13:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zombie101](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zombie101/32/6573_2.png) [@zombie101](https://discuss.elastic.co/u/zombie101)\
**Post date:** [April 4, 2016, 6:13pm UTC](https://discuss.elastic.co/t/logstash-2-3-redis-input-not-compatible-with-redis-2-4-10/46278/1 "2016-04-04T18:13:41Z")

</div>

Just a FYI for anyone else who hits this: I just upgraded to logstash 2.3 and my ELK pipeline broke because my indexers were not able to read from my redis instances, which were running redis 2.4.10 (Default RHEL 6 version). The errors included connection errors, and exception regarding an unknown command:

{:timestamp=\>"2016-04-04T08:44:26.088000-0700", :message=\>"Redis connection problem", :exception=\>#\<Redis::CommandError: ERR unknown command 'script'\>, :level=\>:warn}  
{:timestamp=\>"2016-04-04T08:44:26.088000-0700", :message=\>"Redis connection problem", :exception=\>#\<Redis::CommandError: ERR unknown command 'script'\>, :level=\>:warn}  
{:timestamp=\>"2016-04-04T08:44:26.088000-0700", :message=\>"Redis connection problem", :exception=\>#\<Redis::CommandError: ERR unknown command 'script'\>, :level=\>:warn}  
{:timestamp=\>"2016-04-04T08:44:26.089000-0700", :message=\>"Redis connection problem", :exception=\>#\<Redis::CannotConnectError: Error connecting to Redis on xxxxxxx:6379 (Errno::ECONNREFUSED)\>, :level=\>:warn}  
{:timestamp=\>"2016-04-04T08:44:26.089000-0700", :message=\>"Redis connection problem", :exception=\>#\<Redis::CannotConnectError: Error connecting to Redis on xxxxxx:6379 (Errno::ECONNREFUSED)\>, :level=\>:warn}  
{:timestamp=\>"2016-04-04T08:44:26.089000-0700", :message=\>"Redis connection problem", :exception=\>#\<Redis::CannotConnectError: Error connecting to Redis on xxxxxxx:6379 (Errno::ECONNREFUSED)\>, :level=\>:warn}  
{:timestamp=\>"2016-04-04T08:44:26.089000-0700", :message=\>"Redis connection problem", :exception=\>#\<Redis::CannotConnectError: Error connecting to Redis on xxxxxx:6379 (Errno::ECONNREFUSED)\>, :level=\>:warn}  
{:timestamp=\>"2016-04-04T08:44:26.090000-0700", :message=\>"Redis connection problem", :exception=\>#\<Redis::CannotConnectError: Error connecting to Redis on xxxxxxx:6379 (Errno::ECONNREFUSED)\>, :level=\>:warn}

I was able to resolve this by upgrading to redis 3.0.6. The redis input docs say that redis 2.6+ is recommended, but I think it is a requirement....

John Ouellette

---

<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:** [April 5, 2016, 12:04am UTC](https://discuss.elastic.co/t/logstash-2-3-redis-input-not-compatible-with-redis-2-4-10/46278/2 "2016-04-05T00:04:11Z")

</div>

Did you try a 2.6.X version before upgrading directly to 3?

---

<div class="post-metadata">

**Author:** ![zombie101](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zombie101/32/6573_2.png) [@zombie101](https://discuss.elastic.co/u/zombie101)\
**Post date:** [April 5, 2016, 12:15am UTC](https://discuss.elastic.co/t/logstash-2-3-redis-input-not-compatible-with-redis-2-4-10/46278/3 "2016-04-05T00:15:10Z")

</div>

No, just right to 3.0.6.

---

<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:03am UTC](https://discuss.elastic.co/t/logstash-2-3-redis-input-not-compatible-with-redis-2-4-10/46278/4 "2017-07-06T05:03:58Z")

</div>