I am not able to open Kibana page in my web browser.
Earlier i was able to seen Kibana page in my browser, later i have deleted kibana and logstash service through command "sc delete logstash/kibana" and re-installed logstash and kibana service. and I have followed the steps in the article https://www.ulyaoth.net/resources/tutorial-install-logstash-and-kibana-on-a-windows-server.34/. after that i am not able to load Kibana page on my Browser.
Could you please help me whats going wrong in that and how can I bring up Kibana?
Yes, I have started Kibana from service.msc and it is showing that Kibana is in Started state.
Earlier Kibana was running in http://localhost:5601 but after i have uninstalled and re-installed Kibana service. after that i am unable to access the Kibana service in browser.
Do i need to re-perform all the step as mentioned in above guide article?
same was happening to me once but after deleting cookies and system restart everything works. Why don't yo just run directly elastic bat file, I mean just to check ?
also, I am wondering if what is the data you store, you might use logstash to try it out, make sure you are having the data index in elastic search, otherwise it cannot show up anything unless the Kibana web page brokes up.
Sure, I think you should have the logstash configuration and then you should have the data, it depends on hwat your data source, apache access log? if so, you can refer to logstash and then running the conf file, then everything is done.
After that, go to the Kibana, and choose the index pattern, so that you should see the data on the Kibana console.
Someone else ran into this, on IRC, though I'm not sure if they were able to rectify the problem. They said there was something up with it connecting to elasticsearch on port 9200, are you experiencing similar symptoms?
I have been trying to recreate my problem with Kibana Discovery, Settings, & other blank WEB pages with only the Kibana banner bening displayed. Also I have not been able to find the the original problem which started after applying Ubuntu 14.04 updates. I will continue my investigation.
Installed fresh Ubuntu 14.04 system +ELK. The Client with filebeat will send syslogs after service filebeat restart only. The client is also Ubuntu 14.04. Ran Ubuntu 14.04 updates to both systems, no change to ELK or the client sending syslog info to the ELK server. I will keep trying to recreate my original problem which appeared after applying Ubuntu 14.04 updates.
Lewis Litchfield
Technology Services - Viking Center Lab
University of South Florida Sarasota-Manatee
941-359-4231
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.