I upgraded Kibana to the lastest version about a month ago and it has been working fine. Today however, when I tried to access Kibana I got this error in my browser:
{"statusCode":500,"error":"Internal Server Error","message":"An internal server error occured."}
Ok, that's strange. So I restarted the service "systemctl restart kibana".
Now, when I navigate to Kibana, all configurations is lost. It asks me to add index patterns to see my data. If I navigate to Stack Monitoring, everything looks fine. ES & Logstash are running and everything is green. But navigating Kibana, all is lost, index patterns, dashboards, everything. It even lost my spaces. It basicly look lite a brand new installation.
So, maybe a corrupt index and Kibana created a new one? Which index could I look at to find the old index-patterns? I did not have them backed up..
What version are running? What version did you upgrade from?
Kibana persisted state is stored in an Elasticsearch index specified by configuration setting kibana.index. The default value is .kibana. Are you setting kibana.index configuration? Did your .kibana index get removed from Elasticsearch?
nano /etc/kibana/kibana.yml
Added this row: kibana.index: ".kibana_3"
Restarted Kibana
And now it's all back to normal. For some reason Kibana decided to create a new index for its settings and moved my old settings to .kibana_3. Maybe a bug?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.