<@U03BTNACHNX> im facing issue with DNS for otelcollector deployed in eks with pvt ingress Lb enabl...
g

gopinath nagalla

about 1 year ago
@nitya-signoz im facing issue with DNS for otelcollector deployed in eks with pvt ingress Lb enabled and it is selfhosted when we are hitting otelcollector DNS we are getting 404 page not found service:
signoz-otel-collector                          ClusterIP   172.20.237.48    <none>        14250/TCP,14268/TCP,8081/TCP,8082/TCP,8888/TCP,4317/TCP,4318/TCP   6d
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/actions.ssl-redirect: '{"Type": "redirect", "RedirectConfig":
      "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/group.name: private
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS": 443}]'
    alb.ingress.kubernetes.io/tags: environment=development
    alb.ingress.kubernetes.io/target-type: ip
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"networking.k8s.io/v1","kind":"Ingress","metadata":{"annotations":{"alb.ingress.kubernetes.io/actions.ssl-redirect":"{\"Type\": \"redirect\", \"RedirectConfig\": \"Protocol\": \"HTTPS\", \"Port\": \"443\", \"StatusCode\": \"HTTP_301\"}}","alb.ingress.kubernetes.io/group.name":"private","alb.ingress.kubernetes.io/listen-ports":"[{\"HTTPS\": 443}]","alb.ingress.kubernetes.io/tags":"environment=development","alb.ingress.kubernetes.io/target-type":"ip","kubernetes.io/ingress.class":"alb"},"labels":{"app.kubernetes.io/component":"otel-collector","app.kubernetes.io/instance":"dev-signoz","app.kubernetes.io/managed-by":"Helm","app.kubernetes.io/name":"signoz","app.kubernetes.io/version":"0.51.0","argocd.argoproj.io/instance":"dev-signoz","helm.sh/chart":"signoz-0.49.0"},"name":"signoz-otel-collector","namespace":"scrapinghub"},"spec":{"rules":[{"host":"otel.fev.engineering","http":{"paths":[{"backend":{"service":{"name":"signoz-otel-collector","port":{"number":4318}}},"path":"/*","pathType":"ImplementationSpecific"}]}}]}}
    kubernetes.io/ingress.class: alb
  creationTimestamp: "2024-08-08T10:26:50Z"
  finalizers:
  - group.ingress.k8s.aws/private
  generation: 5
  labels:
    app.kubernetes.io/component: otel-collector
    app.kubernetes.io/instance: dev-signoz
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: signoz
    app.kubernetes.io/version: 0.51.0
    argocd.argoproj.io/instance: dev-signoz
    helm.sh/chart: signoz-0.49.0
  name: signoz-otel-collector
  namespace: scrapingt
  resourceVersion: "899762941"
  uid: e5d0c057-f39e0d18
spec:
  rules:
  - host: otel.fev.engineering
    http:
      paths:
      - backend:
          service:
            name: signoz-otel-collector
            port:
              number: 4318
        path: /*
        pathType: ImplementationSpecific
status:
  loadBalancer:
    ingress:
    - hostname: internal-k8s-private-4ae926.us-west-2.elb.amazonaws.com
https://signoz-community.slack.com/archives/C01HWQ1R0BC/p1719997121751949 please refer this too
Just updated to signoz to 0.77.0 using helm chart, and had an issue with the `signoz-schema-migrator...
p

Pedro Carvalho

5 months ago
Just updated to signoz to 0.77.0 using helm chart, and had an issue with the
signoz-schema-migrator-sync-init
Job. It seems to have an issue with connecting to Zookeeper.
│ {"L":"info","timestamp":"<>","C":"signozschemamigrator/main.go:104","M":"Up migrations","versions":[]}
│ {"L":"info","timestamp":"<>","C":"signozschemamigrator/main.go:117","M":"Down migrations","versions":[]}
│ {"L":"info","timestamp":"<>","C":"signozschemamigrator/main.go:127","M":"Parsed DSN","optsError":"json: unsupported type: func(context.Context, string) (net.Conn, error)"
│ }
│ {"L":"info","timestamp":"<>","C":"signozschemamigrator/main.go:133","M":"Opened connection"}
│ Error: failed to bootstrap migrations: failed to create dbs
│ failed to create dbs
│ code: 999, message: All connection tries failed while connecting to ZooKeeper. nodes: <IPS>
│ Code: 33. DB::Exception: Cannot read all data. Bytes read: 0. Bytes expected: 4.: while receiving handshake from ZooKeeper. (CANNOT_READ_ALL_DATA) (version 24.... (official build)), <IP>
│ Code: 33. DB::Exception: Cannot read all data. Bytes read: 0. Bytes expected: 4.: while receiving handshake from ZooKeeper. (CANNOT_READ_ALL_DATA) (version 24.... (official build)), <IP>
│ Code: 33. DB::Exception: Cannot read all data. Bytes read: 0. Bytes expected: 4.: while receiving handshake from ZooKeeper. (CANNOT_READ_ALL_DATA) (version 24.... (official build)), <IP>
│ Code: 33. DB::Exception: Cannot read all data. Bytes read: 0. Bytes expected: 4.: while receiving handshake from ZooKeeper. (CANNOT_READ_ALL_DATA) (version 24.... (official build)), <IP>
Zookeeper and Clickhouse are hosted externally, and this is the first time I've seen Signoz interact with Zookeeper. I have not even provided any zookeeper address on the helm chart, so I can only assume that the IPS were collected from Clickhouse. I think this issue might be on our end, the machines with ZK might not be accepting any inbound connections except from the CH hosts and the metrics scrapper, but I'm putting this out there in either case.