# Kibana v.2 broken after ES 1.4 Upgrade?

**URL:** <https://discuss.elastic.co/t/kibana-v-2-broken-after-es-1-4-upgrade/20738>\
**Category:** Elasticsearch\
**Created:** [November 13, 2014, 9:18pm UTC](https://discuss.elastic.co/t/kibana-v-2-broken-after-es-1-4-upgrade/20738 "2014-11-13T21:18:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Kleiner](https://avatars.discourse-cdn.com/v4/letter/d/50afbb/32.png) [@David\_Kleiner](https://discuss.elastic.co/u/David_Kleiner)\
**Post date:** [November 13, 2014, 9:18pm UTC](https://discuss.elastic.co/t/kibana-v-2-broken-after-es-1-4-upgrade/20738/1 "2014-11-13T21:18:07Z")

</div>

Hello fellow E/searchers,

After taking a plunge from 1.3.4 to 1.4.0, my Kibana v.2 instance is broken:

[ 2014-11-13 14:26:52.0246 9520/7f41041e5700 Pool2/Implementation.cpp:1172  
]: [App 9567 stderr] NoMethodError - undefined method `count' for nil:NilClass: [2014-11-13 14:26:52.0247 9520/7f41041e5700 Pool2/Implementation.cpp:1172]: [App 9567 stderr] /opt/kb2/lib/kelastic.rb:46:in`all\_indices'  
[ 2014-11-13 14:26:52.0247 9520/7f41041e5700 Pool2/Implementation.cpp:1172  
]: [App 9567 stderr] /opt/kb2/lib/kelastic.rb:45:in `each' [2014-11-13 14:26:52.0247 9520/7f41041e5700 Pool2/Implementation.cpp:1172]: [App 9567 stderr] /opt/kb2/lib/kelastic.rb:45:in`all\_indices'  
[ 2014-11-13 14:26:52.0247 9520/7f41041e5700 Pool2/Implementation.cpp:1172  
]: [App 9567 stderr] /opt/kb2/lib/kelastic.rb:74:in `index_range' [2014-11-13 14:26:52.0247 9520/7f41041e5700 Pool2/Implementation.cpp:1172]: [App 9567 stderr] /opt/kb2/lib/kibana-app.rb:60:in`GET  
/api/search/:hash/?:segment?'  
[ 2014-11-13 14:26:52.0247 9520/7f41041e5700 Pool2/Implementation.cpp:1172  
]: [App 9567 stderr]  
/usr/lib/ruby/gems/1.8/gems/sinatra-1.4.3/lib/sinatra/base.rb:1540:in `call'

I understand that Kibana v.2 hasn't been touched in over a year and Kibana  
v.4 is all the rage now. My Kibana v.3 setup is also working fine, as far  
as I can tell.

Is firing 1.3 client node an option at all? I've seen a posting here  
advising against it and it also breaks v.4 exploration. Just thinking out  
loud here.

Thank you,

David

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ea225492-0ac5-4a38-8f15-14f46985eead%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ea225492-0ac5-4a38-8f15-14f46985eead%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:50am UTC](https://discuss.elastic.co/t/kibana-v-2-broken-after-es-1-4-upgrade/20738/2 "2017-07-06T00:50:05Z")

</div>

Closed on July 6, 2017, 12:50am UTC