kubernetes-elk-cluster icon indicating copy to clipboard operation
kubernetes-elk-cluster copied to clipboard

Kibana unable to connect to elasticsearch

Open VasuBalakrishnan opened this issue 9 years ago • 6 comments

I'm getting these errors when running kibana

{"name":"Kibana","hostname":"kibana-z2aab","pid":7,"level":30,"msg":"Unable to connect to elasticsearch at http://elasticsearch.default.svc.cluster.local:9200. Retrying in 2.5 seconds.","time":"2016-02-11T19:12:16.168Z","v":0}

I tried nslookup and it cannot resolve the service name

kubectl exec kibana-z2aab -- nslookup elasticsearch.default.svc.cluster.local

Server: (null) Address 1: ::1 localhost Address 2: 127.0.0.1 localhost

nslookup: can't resolve 'elasticsearch.default.svc.cluster.local': Name does not resolve error: error executing remote command: Error executing command in container: Error executing in Docker Container: 1

Looks like kubernetes DNS issue. Any ideas / pointers ?

thanks

VasuBalakrishnan avatar Feb 11 '16 19:02 VasuBalakrishnan

Strangely I'm able to resolve the following from kibana pod but I cannot resolve elasticsearch.

kubectl exec kibana-z2aab -- nslookup kubernetes.default.svc.cluster.local

Server: (null) Address 1: ::1 localhost Address 2: 127.0.0.1 localhost

Name: kubernetes.default.svc.cluster.local Address 1: 11.1.2.1

VasuBalakrishnan avatar Feb 11 '16 20:02 VasuBalakrishnan

This is an issue with Alpine Linux containers and DNS. Newer images of the stack are fixed but I haven't got the time to fix #11.

pires avatar Feb 11 '16 20:02 pires

Any timeframe or workaround this?

thanks

VasuBalakrishnan avatar Feb 11 '16 20:02 VasuBalakrishnan

Nop, I'm no longer actively using ELK.

pires avatar Feb 11 '16 21:02 pires

Whats involved in upgrading the stack? I can pitch in.

VasuBalakrishnan avatar Feb 11 '16 21:02 VasuBalakrishnan

See #11.

pires avatar Feb 11 '16 21:02 pires