bland-lighter-26751
12/19/2022, 7:00 PMDisconnected while requesting ApiVersion: might be caused by incorrect security.protocol configuration (connecting to a SSL listener?) or broker version is < 0.10 (see api.version.request) (after 82ms in state APIVERSION_QUERY, 4 identical error(s) suppressed)
My yaml has
springKafkaConfigurationOverrides:
security.protocol: SASL_SSL
sasl.mechanism: PLAIN
client.dns.lookup: use_all_dns_ips
basic.auth.credentials.source: USER_INFO
Any ideas? Was just following this doc: https://datahubproject.io/docs/deploy/confluent-cloud/ which is pretty straightforward. Datahub-gms is running fine and the logs say it was able to connect to the cluster.polite-musician-66972
12/19/2022, 7:42 PMgreat-monkey-52307
12/20/2022, 5:24 AMmicroscopic-twilight-7661
12/20/2022, 10:20 AMError: can't get a valid version for repositories mysql, postgresql, kafka.
I've checked the bitnami repo for the versions used in the prerequisites chart and noticed they are not present so I've used newer versions for these dependencies. Just an FYI if someone gets the same issue and a suggestion to update the versions on these dependencies.bulky-policeman-19038
12/20/2022, 3:48 PMbland-lighter-26751
12/20/2022, 7:48 PMjava.util.concurrent.CompletionException: org.pac4j.core.exception.TechnicalException: Bad token response, error=invalid_grant
My yaml has
- AUTH_OIDC_ENABLED=true
- AUTH_OIDC_CLIENT_ID=${AUTH_OIDC_CLIENT_ID}
- AUTH_OIDC_CLIENT_SECRET=${AUTH_OIDC_CLIENT_SECRET}
- AUTH_OIDC_DISCOVERY_URI=${AUTH_OIDC_DISCOVERY_URI}
- AUTH_OIDC_BASE_URL=<http://localhost:9002>
- AUTH_OIDC_SCOPE=${AUTH_OIDC_SCOPE}
- AUTH_OIDC_USER_NAME_CLAIM=email
- AUTH_OIDC_USER_NAME_CLAIM_REGEX=([^@]+)
Any ideas on what the problem is or how I can debug further? I did a search and saw a couple others had this issue but never found a way to resolve it.late-book-30206
12/21/2022, 10:25 AMthankful-fireman-70616
12/21/2022, 4:34 PMplain-cricket-83456
12/22/2022, 2:00 AMagreeable-park-13466
12/22/2022, 12:14 PMdatahub:
version: v0.9.3
gms:
port: "8080"
nodePort: "30001"
careful-nightfall-53251
12/22/2022, 3:44 PMlimited-forest-73733
12/26/2022, 10:39 AMblue-honey-61652
12/26/2022, 11:48 AMbest-daybreak-64419
12/26/2022, 6:50 AMkubectl get pods
command, the prerequisites-mysql-0
pod is continuously restarting.
So I redeployed the prerequistites
repo. However, the pod is still running again. Attach log image of prerequisites-mysql-0
.
What should I do?flaky-businessperson-14858
12/27/2022, 4:41 AMpowerful-cat-68806
12/27/2022, 10:08 AMflaky-businessperson-14858
12/27/2022, 4:43 AM# Required Environment Variables
EBEAN_DATASOURCE_USERNAME=datahub
EBEAN_DATASOURCE_PASSWORD=datahub
EBEAN_DATASOURCE_HOST=de-test-3:3306
EBEAN_DATASOURCE_URL=jdbc:<mysql://de-test-3:3306/datahub?verifyServerCertificate=false&useSSL=true&useUnicode=yes&characterEncoding=UTF-8>
EBEAN_DATASOURCE_DRIVER=com.mysql.jdbc.Driver
KAFKA_BOOTSTRAP_SERVER=de-test-3:9092
KAFKA_SCHEMAREGISTRY_URL=<http://de-test-3:8081>
ELASTICSEARCH_HOST=de-test-3
ELASTICSEARCH_PORT=9200
DATAHUB_GMS_HOST=de-test-3
DATAHUB_GMS_PORT=8080
delightful-sunset-48960
12/27/2022, 8:13 PMmaster
deployment from the Helm chart in this PR: https://github.com/acryldata/datahub-helm/pull/224blue-honey-61652
12/28/2022, 9:07 AM2022/12/28 08:41:12 Waiting for: <http://elasticsearch-master:9200>
2022/12/28 08:41:12 Received 200 from <http://elasticsearch-master:9200>
Going to use protocol: http
Going to use default elastic headers
Create datahub_usage_event if needed against Elasticsearch at elasticsearch-master:9200
Going to use index prefix::
curl: option -k <http://elasticsearch-master:9200/_ilm/policy/datahub_usage_event_policy>: is unknown
curl: try 'curl --help' or 'curl --manual' for more information
/create-indices.sh: line 41: [: -eq: unary operator expected
/create-indices.sh: line 45: [: -eq: unary operator expected
/create-indices.sh: line 47: [: -eq: unary operator expected
2022/12/28 08:41:12 Command exited with error: exit status 1
Policy GET response code is
Got response code while creating policy so exiting.
flaky-painting-93216
12/28/2022, 11:25 AMhelm install datahub datahub/datahub --values <my_values>.yaml
it creates ELB and S*ecurity Group* (Description: ”_Security group for Kubernetes ELB <name_id> (default/datahub-datahub-gms)_”) which allows traffic from 0.0.0.0/0 to ports 8080 and 4318.
How can I limit the sources in the security group inbound rules so that it doesn’t allow 0.0.0.0/0, but only limited sources, or is it necessary to have it with 0.0.0.0/0 sources?wonderful-vegetable-45135
12/28/2022, 2:15 PMcuddly-butcher-39945
12/28/2022, 6:54 PM/tmp/datahub/logs/gms or datahub-frontend: /tmp/datahub/logs/datahub-frontend
The deployed version is 0.9.3
Any help would be appreciated.
great-monkey-52307
12/28/2022, 8:45 PMbetter-orange-49102
12/29/2022, 1:25 AMaloof-energy-17918
12/29/2022, 2:06 AMaloof-energy-17918
12/29/2022, 2:10 AMwonderful-vegetable-45135
12/30/2022, 2:12 PMwonderful-vegetable-45135
12/30/2022, 2:12 PMcurved-planet-99787
01/02/2023, 3:24 PM0.9.3
).
Consequently, we only get an empty analytics page shown in the UI.
We could fix this by running
curl -XPUT '<http://localhost:9200/_data_stream/datahub_usage_event>'
manually.
Is this a known issue? Has anyone an idea how to integrate this command in the datahub deployment so that we don't need to execute it manually for every deployment?better-orange-49102
01/03/2023, 8:09 AM