search

confluentinc / confluent-kubernetes-examples

Example scenario workflows for Confluent for Kubernetes
Apache License 2.0
42 stars 176 forks source link

Schemaregistry - Unexpected 4xx health check response #94

Open nmsaini opened 2 years ago

nmsaini commented 2 years ago

I am seeing the following warning in my control center logs which I am unable to figure out.

It seems somewhere internally there is a healthcheck being done to a authorized endpoint. In this case a 401 should a good response.

[2022-01-03 16:33:03,175] WARN [armeria-common-worker-epoll-2-1] [creqId=a3f89d66, chanId=5ea82cd4, laddr=10.254.12.29:54770, raddr=schemaregistry.confluent.svc.cluster.local/10.254.12.22:8081][https://schemaregistry.confluent.svc.cluster.local:8081/#GET] Unexpected 4xx health check response: [:status=401, www-authenticate=basic realm="SchemaRegistry-Props", content-type=application/json;charset=iso-8859-1, content-length=43] A 4xx response generally indicates a misconfiguration of the client. Did you happen to forget to configure the HealthCheckedEndpointGroup's client options? (com.linecorp.armeria.client.endpoint.healthcheck.HttpHealthChecker)

It is only a warning, so not a huge issue.

arizaa commented 9 months ago

I have the same problem. Does anyone have any ideas?

arizaa commented 9 months ago

it would help if you used this variable in the control center. CONTROL_CENTER_CONNECT_HEALTHCHECK_ENDPOINT: '/connectors'