Issues Running ElasticSearch on Kibana

Elastic Stack Elasticsearch
1

Hey all. I'm brand new to running Kibana, and I'm using a software called GrimoireLab that runs off of it and docker. I used to not have any issues setting it up, but every time I try to open my localhost now it says ERROR: KIBANA STATUS IS RED. The only error I can see is with Elasticsearch, which has a timeout error. My usual way of fixing it by changing the Elasticsearch size isn't working. Below is my localhost:9200 output.

{
  "name" : "pFg0LCd",
  "cluster_name" : "docker-cluster",
  "cluster_uuid" : "9NpeH35UT3CkB1ts4sN3kg",
  "version" : {
    "number" : "6.8.6",
    "build_flavor" : "oss",
    "build_type" : "docker",
    "build_hash" : "3d9f765",
    "build_date" : "2019-12-13T17:11:52.013738Z",
    "build_snapshot" : false,
    "lucene_version" : "7.7.2",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}

I'm a complete noob to docker, so I'm not sure where to find the server output. Thanks in advance!

2

The error message you're seeing indicates that Kibana is unable to connect to Elasticsearch, which is why the status is red. This could be due to a number of reasons, such as Elasticsearch not running, network connectivity issues, or configuration problems.

Since you're seeing a timeout error with Elasticsearch, it's possible that Elasticsearch is not running or is not accessible from Kibana. Here are some steps you can take to troubleshoot this issue:

  1. Check if Elasticsearch is running: You can do this by running the command curl localhost:9200 in your terminal. If Elasticsearch is running, you should see a JSON response with information about your Elasticsearch cluster.
  2. Check the network connectivity: If Elasticsearch is running, the next step is to check if Kibana can reach Elasticsearch over the network. You can do this by running a ping command from the Kibana server to the Elasticsearch server.
  3. Check the Kibana configuration: If both of the above steps are successful, the issue might be with the Kibana configuration. Check the kibana.yml file to ensure that the elasticsearch.hosts setting is correctly pointing to your Elasticsearch server.
  4. Check the Elasticsearch logs: If you're still unable to resolve the issue, you should check the Elasticsearch logs for any error messages. Since you're running Elasticsearch in Docker, you can view the logs by running the command docker logs <container_id>, replacing <container_id> with the ID of your Elasticsearch container.

If your cluster is in a red state, it means that some data is unavailable. This could be due to unassigned shards. You can investigate unassigned shards by running the following command in the Kibana Dev Tools console:

GET _cluster/allocation/explain?filter_path=index,shard,primary,**.node_name,**.node_decision,**.decider,**.decision,**.*explanation,**.unassigned_info,**.*delay

”Disclaimer, OpsGPT assisted me with this answer.”

3

Hello, the curl is failing and I cannot get a JSON response. What would be the next steps in fixing this?

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.