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:inall_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:inall_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:inGET
/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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ea225492-0ac5-4a38-8f15-14f46985eead%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.