# Upgrade to 2.0 breaks Kibana and Logstash

**URL:** <https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953>\
**Category:** Elasticsearch\
**Created:** [October 10, 2015, 2:44pm UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953 "2015-10-10T14:44:22Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![scaarup](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scaarup/32/4615_2.png) [@scaarup](https://discuss.elastic.co/u/scaarup)\
**Post date:** [October 10, 2015, 2:44pm UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/1 "2015-10-10T14:44:22Z")

</div>

Hi all.

I just tried to upgrade my elasticsearch from 1.7 to 2.0 on a non-prod system. I have not upgraded logstash or Kibana. Kibana (1.4.2) just stopped working with an error "  
Error  
Discover: An error occurred with your request. Reset your inputs and try again." And when I start logstash (1.5.4), the elasticsearch.log is filled with below exceptions:

[2015-10-10 16:36:17,099][WARN][org.elasticsearch.transport.netty] [S'ym] exception caught on transport layer [[id: 0x2d7d20c7, /127.0.0.1:55205 =\> /127.0.0.1:9300]], closing connection  
java.lang.IllegalStateException: Message not fully read (request) for requestId [2079], action [internal:discovery/zen/unicast\_gte\_1\_4], readerIndex [59] vs expected [215]; resetting  
at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:120)  
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)  
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)  
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)  
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)  
at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)  
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)  
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)  
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)  
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)  
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)  
at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:75)  
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)  
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)  
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)  
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)  
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)  
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)  
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)  
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)  
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)  
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)  
at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  
at java.lang.Thread.run(Thread.java:745)

I could not find any documentation saying, that I have to upgrade kibana and logstash as well, but do I?

---

<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:** [October 11, 2015, 2:08am UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/2 "2015-10-11T02:08:21Z")

</div>

You need to use KB 4.2 if you want to use ES 2.0, 4.1 is not compatible.

LS should still work though, what protocol are you using to talk to it?

---

<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:** [October 11, 2015, 8:07pm UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/3 "2015-10-11T20:07:42Z")

</div>

> [2015-10-10 16:36:17,099][WARN][org.elasticsearch.transport.netty] [S'ym] exception caught on transport layer [[id: 0x2d7d20c7, /127.0.0.1:55205 =\> /127.0.0.1:9300]], closing connection

You should not expect Logstash 1.5 to work with ES 2.0 unless you use the HTTP protocol (which will be the default in Logstash 2.0).

---

<div class="post-metadata">

**Author:** ![scaarup](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scaarup/32/4615_2.png) [@scaarup](https://discuss.elastic.co/u/scaarup)\
**Post date:** [October 14, 2015, 10:49am UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/4 "2015-10-14T10:49:22Z")

</div>

Aha okay. Will look into that then.

---

<div class="post-metadata">

**Author:** ![scaarup](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scaarup/32/4615_2.png) [@scaarup](https://discuss.elastic.co/u/scaarup)\
**Post date:** [October 15, 2015, 11:51am UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/5 "2015-10-15T11:51:06Z")

</div>

As far as I can read, the logstash-forwarder only supports the lumberjack protocol. How can I forward logs via HTTP?

---

<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:** [October 15, 2015, 12:41pm UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/6 "2015-10-15T12:41:07Z")

</div>

LSF can continue to submit logs via Lumberjack to Logstash, which then sends them to ES via HTTP.

---

<div class="post-metadata">

**Author:** ![scaarup](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scaarup/32/4615_2.png) [@scaarup](https://discuss.elastic.co/u/scaarup)\
**Post date:** [October 15, 2015, 12:42pm UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/7 "2015-10-15T12:42:19Z")

</div>

Aha, that way around. Thanks

---

<div class="post-metadata">

**Author:** ![rsjavier](https://avatars.discourse-cdn.com/v4/letter/r/9e8a1a/32.png) [@rsjavier](https://discuss.elastic.co/u/rsjavier)\
**Post date:** [November 5, 2015, 11:32am UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/8 "2015-11-05T11:32:24Z")

</div>

Hi Magnus,

I have ES 2.0 and LS 1.5.4 and my output to elasticsearch is thru http.  
elasticsearch { protocol =\> "http" host =\> "10.0.0.35:9200" index =\> "logstash-%{+YYYY.MM.dd}"}

The new index will be created but in red status and no data is being inserted.  
red open logstash-2015.11.05 5 1

Here are some errors in logstash.log  
{:timestamp=\>"2015-11-05T06:17:43.074000-0500", :message=\>"retrying failed action with response code: 503", :level=\>:warn}

What could be wrong?

---

<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:** [November 5, 2015, 11:53am UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/9 "2015-11-05T11:53:05Z")

</div>

@rsjavier, please start a new thread for your unrelated question.

---

<div class="post-metadata">

**Author:** ![rsjavier](https://avatars.discourse-cdn.com/v4/letter/r/9e8a1a/32.png) [@rsjavier](https://discuss.elastic.co/u/rsjavier)\
**Post date:** [November 9, 2015, 1:39am UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/10 "2015-11-09T01:39:34Z")

</div>

OK, I will create one but I upgraded also my ES 1.4.2 to ES 2.0 when I encounter the error.

Thanks!

---

<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 5, 2017, 11:39pm UTC](https://discuss.elastic.co/t/upgrade-to-2-0-breaks-kibana-and-logstash/31953/11 "2017-07-05T23:39:53Z")

</div>


