# Updated to 1.6.1 and seeing an issue. Time to jump to 1.7? **URL:** \ **Category:** Logstash\ **Created:** [July 21, 2015, 6:59pm UTC](https://discuss.elastic.co/t/updated-to-1-6-1-and-seeing-an-issue-time-to-jump-to-1-7/26013 "2015-07-21T18:59:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![bdunbar](https://avatars.discourse-cdn.com/v4/letter/b/a3d4f5/32.png) [@bdunbar](https://discuss.elastic.co/u/bdunbar)\ **Post date:** [July 21, 2015, 6:59pm UTC](https://discuss.elastic.co/t/updated-to-1-6-1-and-seeing-an-issue-time-to-jump-to-1-7/26013/1 "2015-07-21T18:59:24Z")
I have four ES nodes, one of which is a client, and is streaming archived log data into the cluster. After upgrading all nodes to 1.6.1. [1] I restarted my intake script. While it appears to be adding data, it's also feeding this back to stdin. Is this a _problem_? Should I make the lightspeed jump to 1.7? Move everyone back to 1.6 ? ``` Jul 21 11:53:44 ris-webstats01 muo_month_3_cache.sh: /stud/buffer.rb:216:in `buffer_flush'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.19/lib/stud/buffer.rb:193:in `buffer_flush'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.19/lib/stud/buffer.rb:159:in `buffer_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-0.2.4-java/lib/logstash/outputs/elasticsearch.rb:426:in `receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-1.5.0-java/lib/logstash/outputs/base.rb:88:in `handle'", "(eval):159:in `output_func'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-1.5.0-java/lib/logstash/pipeline.rb:244:in `outputworker'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-1.5.0-java/lib/logstash/pipeline.rb:166:in `start_outputs'"], :level=>:warn} ``` [1] I added a third data node, which yum helpfully installed at 1.6.1 which caused issues with shards. The _previous_ three nodes installed, weeks before, with 1.6.0. ---
**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:** [July 23, 2015, 7:01am UTC](https://discuss.elastic.co/t/updated-to-1-6-1-and-seeing-an-issue-time-to-jump-to-1-7/26013/2 "2015-07-23T07:01:46Z")
That's a Logstash problem not an ES one. What version of LS are you on? ---
**Author:** ![bdunbar](https://avatars.discourse-cdn.com/v4/letter/b/a3d4f5/32.png) [@bdunbar](https://discuss.elastic.co/u/bdunbar)\ **Post date:** [July 23, 2015, 2:57pm UTC](https://discuss.elastic.co/t/updated-to-1-6-1-and-seeing-an-issue-time-to-jump-to-1-7/26013/3 "2015-07-23T14:57:10Z")
``` # /opt/logstash/bin/logstash --version logstash 1.5.0 ``` ---
**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:** [July 23, 2015, 8:46pm UTC](https://discuss.elastic.co/t/updated-to-1-6-1-and-seeing-an-issue-time-to-jump-to-1-7/26013/4 "2015-07-23T20:46:18Z")
Upgrade LS to \>1.5.2, there are some fixes there that will help. ---
**Author:** ![bdunbar](https://avatars.discourse-cdn.com/v4/letter/b/a3d4f5/32.png) [@bdunbar](https://discuss.elastic.co/u/bdunbar)\ **Post date:** [July 23, 2015, 8:54pm UTC](https://discuss.elastic.co/t/updated-to-1-6-1-and-seeing-an-issue-time-to-jump-to-1-7/26013/5 "2015-07-23T20:54:08Z")
> [@bdunbar](#): > > /opt/logstash/bin/logstash --version Yum offered to update me to 1.5.3. After I did so this was thrown into /var/log/logstash. It _seems_ to be feeding the bits into elasticsearch okay .. ``` cat logstash.err '[DEPRECATED] use `require 'concurrent'` instead of `require 'concurrent_ruby'` ``` ---
**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:33am UTC](https://discuss.elastic.co/t/updated-to-1-6-1-and-seeing-an-issue-time-to-jump-to-1-7/26013/6 "2017-07-06T05:33:55Z")
Closed on July 6, 2017, 5:33am UTC