– ERROR lookup logstash : no such host – ERROR lookup logstash : no such host

Problem Description:

I’m deploying ELK on k8s but getting error on Filebeat

kubectl describe pod filebeat-filebeat-rpjbg -n elk ///


Warning  Unhealthy  8s (x5 over 48s)  kubelet            Readiness probe failed: logstash: logstash:5044...
    parse host... OK
    dns lookup... ERROR lookup logstash on no such host

In logstash values.yaml may be this causing error?

  logstash.yml: |
    xpack.monitoring.enabled: false


NAME                      READY   STATUS    RESTARTS   AGE
elasticsearch-master-0    1/1     Running   0          146m
filebeat-filebeat-rpjbg   0/1     Running   0          5m45s
filebeat-filebeat-v4fxz   0/1     Running   0          5m45s
filebeat-filebeat-zf5w7   0/1     Running   0          5m45s
logstash-logstash-0       1/1     Running   0          14m
logstash-logstash-1       1/1     Running   0          14m
logstash-logstash-2       1/1     Running   0          14m


NAME                            TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
elasticsearch-master            ClusterIP   <none>        9200/TCP,9300/TCP   172m
elasticsearch-master-headless   ClusterIP   None             <none>        9200/TCP,9300/TCP   172m
logstash-logstash               ClusterIP   <none>        5044/TCP            16m
logstash-logstash-headless      ClusterIP   None             <none>        9600/TCP            16m

elasticsearch – values.yaml

logstash – values.yaml

filebeat – values.yaml

Solution – 1

Filebeat is trying to resolve "logstash", but you don’t have a service with that name. You have "logstash-logstash". Try to change filebeat config (line 49 and 116 in filebeat values.yaml) or change the name of your logstash service accordingly.

Rate this post
We use cookies in order to give you the best possible experience on our website. By continuing to use this site, you agree to our use of cookies.