Type to search.

Error: Kibana server is not ready yet

ECH

Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

ECK

Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

ECE

Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Self-managed

Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

To troubleshoot the Kibana server is not ready yet error, try these steps:

  1. From within a Kibana node, confirm the connection to Elasticsearch:

    Shell 
    curl -XGET elasticsearch_ip_or_hostname:9200/

  2. Guarantee the health of the three Kibana-backing indices. All indices must appear and display status:green and status:open:

    Shell 
    curl -XGET elasticsearch_ip_or_hostname:9200/_cat/indices/.kibana,.kibana_task_manager,.kibana_security_session,.security*?v=true

    These Kibana-backing indices must also not have index settings flagging read_only_allow_delete or write index blocks.

  3. Shut down all Kibana nodes.

  4. Choose any Kibana node, then update the config to set the debug logging.

  5. Start the node, then check the start-up debug logs for ERROR messages or other start-up issues.

    For example:

    • When Kibana is unable to connect to a healthy Elasticsearch cluster, errors like master_not_discovered_exception or unable to revive connection or license is not available errors appear.
    • When one or more Kibana-backing indices are unhealthy, the index_not_green_timeout error appears.