-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logstash 1.4.2 running in "node" mode stops Kibana 4 from working #1542
Comments
For short term I would try changing the requirement in index.js src/kibana/index.js and see if you still have issues |
Hi, Kibana 4 requires that all nodes in the cluster meet the minimum version requirements. If you're using logstash the work around is to use the elasticsearch-http output in Logstash. |
@kkirsche You mention changing the requirements in the index.js file. How can I do that since the release is just a jar. Are there instructions on building Kibana 4 from source somewhere? |
Ah. Sorry. I was using a clone of the github source. I'm not familiar with building it into a jar from source. I will say that you can get Kibana up and running by cloning the repo, then going into src/server/README.md and following the instructions to get the server up. Check out pull request #1538 for two commands that were missing that are necessary to go from cloned to running. Hope that helps @bradvido |
Tried running Kibana 4 on a local machine with ES 1.4.0.Beta1 and using Logstash 1.4.2 to push some events to it. Kibana stoped working.
I believe this is the case because LS register itself as a Node and Kibana checks if all nodes are on 1.4.0.Beta1.
There is any solution on this? If I run LS in transport mode all is fine.
Dunno if this is a bug, a feature request or just a "wait for LS 1.5 with Kibana 4" issue...
The text was updated successfully, but these errors were encountered: