Kibana fails with error EHOSTUNREACH while attempting to connect elasticsearch pod

Solution Verified - Updated -

Issue

  • Following are the errors seen on the kibana pod logs

{"type":"log","@timestamp":"2018-01-30T04:19:17Z","tags":["error","elasticsearch"],"pid":15,"message":"Request error, retrying -- connect EHOSTUNREACH 192.xx.xx.xx:9200"} {"type":"log","@timestamp":"2018-01-30T04:19:19Z","tags":["status","plugin:elasticsearch@1.0.0","error"],"pid":15,"state":"red","message":"Status changed from green to red - Request Timeout after 3000ms","prevState":"green","prevMsg":"Kibana index ready"} {"type":"response","@timestamp":"2018-01-30T04:19:20Z","tags":[],"pid":15,"method":"head","statusCode":200,"req":{"url":"/","method":"head","headers":{"user-agent":"curl/7.29.0","host":"localhost:5601","accept":"*/*"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1"},"res":{"statusCode":200,"responseTime":13,"contentLength":9},"message":"HEAD / 200 13ms - 9.0B"}
  • Elasticsearch pod logs have the following errors as well
Contacting elasticsearch cluster 'elasticsearch' and wait for YELLOW clusterstate ...
Clustername: logging-es
Clusterstate: YELLOW
Number of nodes: 3
Number of data nodes: 3
.searchguard.logging-es-data-master-4pstbk3d index already exists, so we do not need to create one.
INFO: .searchguard.logging-es-data-master-4pstbk3d index state is YELLOW, it seems you miss some replicas
Populate config from /opt/app-root/src/sgconfig/

Environment

  • OpenShift Container Platform (OCP)
    • 3.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.