Error while curling svc.cluster.local

john2 · January 30, 2020, 6:52am

Hello, i've followed your instructions here at https://docs.mae.sh/examples/

[root@kubemaster maesh]# kubectl -n whoami exec whoami-client -- curl -s whoami.whoami.svc.cluster.local
command terminated with exit code 6

[root@kubemaster maesh]# kubectl get pods -n whoami
NAME                          READY   STATUS    RESTARTS   AGE
whoami-8cc58c56c-fwtz4        1/1     Running   0          6m40s
whoami-8cc58c56c-wzd4q        1/1     Running   0          6m40s
whoami-client                 1/1     Running   0          6m40s
whoami-tcp-7f958d57bd-476q7   1/1     Running   0          6m40s
whoami-tcp-7f958d57bd-jms7r   1/1     Running   0          6m40s

daniel.tomcej · February 3, 2020, 6:00pm

Hello @john2,

Curl error code 6 means that it could not resolve the host.

Can you please give us some more information about your kubernetes environment?
whoami.whoami.svc.cluster.local should resolve if your kubernetes DNS is configured correctly, and you have a whoami service.

john2 · February 3, 2020, 6:08pm

[root@kubemaster maesh]# kubectl get svc -n whoami
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
whoami       ClusterIP   10.110.246.170   <none>        80/TCP     3d9h
whoami-tcp   ClusterIP   10.98.89.106     <none>        8080/TCP   3d9h

[root@kubemaster maesh]# kubectl get pods -n kube-system
NAME                                 READY   STATUS    RESTARTS   AGE
coredns-569c666dd4-6wr9x             1/1     Running   2          3d9h
coredns-569c666dd4-d9fsl             1/1     Running   2          3d9h
etcd-kubemaster                      1/1     Running   2          3d10h
kube-apiserver-kubemaster            1/1     Running   2          116m
kube-controller-manager-kubemaster   1/1     Running   2          3d10h
kube-flannel-ds-amd64-jvcb8          1/1     Running   2          3d10h
kube-flannel-ds-amd64-s2d7f          1/1     Running   2          3d10h
kube-flannel-ds-amd64-vr2j4          1/1     Running   2          3d10h
kube-proxy-7rs9l                     1/1     Running   2          3d10h
kube-proxy-bz4vd                     1/1     Running   2          3d10h
kube-proxy-kbm4z                     1/1     Running   2          3d10h
kube-scheduler-kubemaster            1/1     Running   3          3d10h

[root@kubemaster maesh]# kubectl get pods -n maesh
NAME                               READY   STATUS    RESTARTS   AGE
grafana-core-7b45f496fd-mg87j      0/1     Pending   0          78m
jaeger-787f575fbd-kt6bp            1/1     Running   0          78m
maesh-controller-dd4ccb4d7-mbkcf   0/1     Running   0          78m
maesh-mesh-67d7z                   1/1     Running   0          78m
maesh-mesh-lbcpr                   0/1     Running   0          78m
prometheus-core-7666b4c94-6phfl    0/2     Pending   0          78m

daniel.tomcej · February 3, 2020, 6:35pm

Hello @john2,

the maesh-controller-dd4ccb4d7-mbkcf 0/1 means that the controller is not ready, and it has not been able to successfully deploy to all maesh nodes.

Can you please get the logs for the controller?

kubectl logs -n maesh maesh-controller-dd4ccb4d7-mbkcf ?

Thanks

john2 · February 3, 2020, 6:45pm

time="2020-02-03T18:44:40Z" level=debug msg="No TrafficTargets with destination in namespace: whoami"
time="2020-02-03T18:44:40Z" level=debug msg="Found traffictargets for service whoami/whoami: []"
time="2020-02-03T18:44:40Z" level=debug msg="Found applicable traffictargets for service whoami/whoami: []"
time="2020-02-03T18:44:40Z" level=debug msg="Found grouped traffictargets for service whoami/whoami: map[]"
time="2020-02-03T18:44:40Z" level=debug msg="No TrafficSplits in namespace: whoami"
time="2020-02-03T18:44:40Z" level=debug msg="Found trafficsplits for service whoami/whoami: []"
time="2020-02-03T18:44:40Z" level=debug msg="Deploying to pod maesh-mesh-67d7z with IP 10.244.2.75"
time="2020-02-03T18:44:40Z" level=debug msg="Deploying to pod maesh-mesh-8ccd5 with IP 10.244.1.70"
time="2020-02-03T18:44:40Z" level=debug msg="Successfully deployed configuration to pod (maesh-mesh-67d7z:10.244.2.75)"
time="2020-02-03T18:45:10Z" level=debug msg="Deploying configuration to unready nodes"
time="2020-02-03T18:45:10Z" level=debug msg="Deploying to pod maesh-mesh-8ccd5 with IP 10.244.1.70"

john2 · February 3, 2020, 6:46pm

  Normal   Scheduled  <unknown>               default-scheduler    Successfully assigned maesh/maesh-controller-dd4ccb4d7-6wjmx to kubeslave2
  Normal   Pulled     3m46s                   kubelet, kubeslave2  Container image "containous/maesh:v1.1.0-rc1" already present on machine
  Normal   Created    3m46s                   kubelet, kubeslave2  Created container maesh-prepare
  Normal   Started    3m45s                   kubelet, kubeslave2  Started container maesh-prepare
  Normal   Pulled     3m45s                   kubelet, kubeslave2  Container image "containous/maesh:v1.1.0-rc1" already present on machine
  Normal   Created    3m45s                   kubelet, kubeslave2  Created container maesh-controller
  Normal   Started    3m44s                   kubelet, kubeslave2  Started container maesh-controller
  Warning  Unhealthy  3m23s (x19 over 3m41s)  kubelet, kubeslave2  Readiness probe failed: HTTP probe failed with statuscode: 500

john2 · February 3, 2020, 7:03pm

I'm installing maesh on my desktop kubernetes cluster. That error comes from my AWS CLuster

john2 · February 4, 2020, 7:43am

@daniel.tomcej, hello how can i disable the checking of new version. My cluster doesnt have an internet connection

time="2020-02-04T07:08:33Z" level=info msg="Starting provider *rest.Provider {\"insecure\":true}"
time="2020-02-04T07:18:48Z" level=warning msg="Error checking new version: Get https://update.traefik.io/repos/containous/traefik/releases: dial tcp: i/o timeout"

[root@kubemaster maesh-master]# kubectl get pods -n maesh
NAME                                READY   STATUS    RESTARTS   AGE
grafana-core-7b45f496fd-hv6h7       0/1     Pending   0          37m
jaeger-787f575fbd-xshnz             1/1     Running   0          37m
maesh-controller-55d8d58f78-rx6hp   0/1     Running   0          37m
maesh-mesh-k5hll                    0/1     Running   0          37m
maesh-mesh-zslzr                    1/1     Running   0          37m
prometheus-core-7666b4c94-q7jvk     0/2     Pending   0          37m

john2 · February 5, 2020, 8:31am

Hello @daniel.tomcej @SantoDE

[root@kubemaster petervient.cipriano]# kubectl get pods -n maesh
NAME                                READY   STATUS    RESTARTS   AGE
grafana-core-7b45f496fd-hv6h7       0/1     Pending   0          25h
jaeger-787f575fbd-r7fdb             1/1     Running   0          77m
maesh-controller-55d8d58f78-mvxf8   1/1     Running   0          76m
maesh-mesh-82bv9                    1/1     Running   0          91m
maesh-mesh-zslzr                    1/1     Running   0          25h
prometheus-core-7666b4c94-q7jvk     0/2     Pending   0          25h

* Could not resolve host: whoami.whoami.svc.cluster.local
* Expire in 200 ms for 1 (transfer 0x56252223e620)
* Closing connection 0
command terminated with exit code 6

daniel.tomcej · February 5, 2020, 1:44pm

Hello @john2,

Is cluster.local your cluster suffix?

If you cannot resolve service names in your cluster, you may have to work on your cluster configuration to make it work.

Maesh relies on DNS to work properly, so it if is not properly configured in k8s, maesh will not work properly.

Topic		Replies	Views
Resolve Same URL on Host and Inside Container Traefik v2 docker	4	2457	January 19, 2023
Traefik stalls while connecting to service Traefik v2 cli	1	336	March 4, 2023
Deployed whoami service, but cant get response Traefik v2 dashboard-api	1	581	December 9, 2020
Followed "quick start" but http "whoami" returns 404, what is wrong ? [help needed] [in progress] Traefik v2 docker , cli	3	2692	December 31, 2019
Can not reproduce Traefik quick start. Getting http 503 error Traefik v2 docker	4	818	May 13, 2023

Error while curling svc.cluster.local

Related topics