witty-motorcycle-52108
11/16/2022, 5:36 PMmysterious-motorcycle-80650
11/16/2022, 6:03 PMgentle-tailor-78929
11/16/2022, 8:38 PMWaiting for: <tcp://localhost:3306>
Problem with dial: dial tcp 127.0.0.1:3306: connect: connection refused. Sleeping 1s
Any idea what could be wrong?bland-orange-13353
11/17/2022, 9:01 AMacceptable-glass-96188
11/17/2022, 11:24 PMrich-van-74931
11/18/2022, 10:14 AMfresh-cricket-75926
11/18/2022, 11:19 AMripe-tailor-61058
11/18/2022, 2:57 PMfaint-tiger-13525
11/21/2022, 8:15 AMshy-parrot-64120
11/21/2022, 10:45 AM0.9.2.3
/ 0.9.3
release dates?
need to plan our compatibility releases (Jinja2
stuff) due to contributions made into main branchblue-honey-61652
11/21/2022, 12:13 PMsecurityContext:
capabilities:
add: ["NET_ADMIN"]
I didn't find anything in the helm chart's values.yaml that would allow me to do that.
Is there a way to do that with the current helm chart ? If the answer is no do you have ideas for workaround/alternative please ^^ ?
Regards,bumpy-eye-36525
11/22/2022, 4:22 AMDisconnected 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 1ms in state APIVERSION_QUERY, 1 identical error(s) suppressed)
fresh-cricket-75926
11/22/2022, 12:12 PMkill -9
on the process.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1."
Any suggestion will be very helpful since we are stuck with this issue from few days.
Attached is the docker build logssilly-angle-91497
11/22/2022, 6:28 PMgentle-tailor-78929
11/22/2022, 6:53 PM[main] INFO org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=localhost:2181 sessionTimeout=40000 watcher=io.confluent.admin.utils.ZookeeperConnectionWatcher@cc34f4d
[FATAL][2022-11-22 18:49:09 +0000] [main] INFO org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
[FATAL][2022-11-22 18:49:09 +0000] [main] INFO org.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 4194304 Bytes
[FATAL][2022-11-22 18:49:09 +0000] [main] INFO org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=
[FATAL][2022-11-22 18:49:09 +0000] [main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
[FATAL][2022-11-22 18:49:09 +0000] [main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Socket error occurred: localhost/127.0.0.1:2181: Connection refused
Kafka setup
[kafka-admin-client-thread | adminclient-1] INFO org.apache.kafka.common.network.SaslChannelBuilder - [AdminClient clientId=adminclient-1] Failed to create channel due to
[FATAL][2022-11-22 18:49:09 +0000] org.apache.kafka.common.errors.SaslAuthenticationException: Failed to configure SaslClientAuthenticator
[FATAL][2022-11-22 18:49:09 +0000] Caused by: org.apache.kafka.common.KafkaException: Principal could not be determined from Subject, this may be a transient failure due to Kerberos re-login
Schema registry
[main] INFO org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=localhost:2181 sessionTimeout=40000 watcher=io.confluent.admin.utils.ZookeeperConnectionWatcher@cc34f4d
[FATAL][2022-11-22 18:49:09 +0000] [main] INFO org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
[FATAL][2022-11-22 18:49:09 +0000] [main] INFO org.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 4194304 Bytes
[FATAL][2022-11-22 18:49:09 +0000] [main] INFO org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=
[FATAL][2022-11-22 18:49:09 +0000] [main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
[FATAL][2022-11-22 18:49:09 +0000] [main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Socket error occurred: localhost/127.0.0.1:2181: Connection refused
refined-energy-76018
11/23/2022, 10:04 AMmicroscopic-mechanic-13766
11/23/2022, 11:46 AMwitty-motorcycle-52108
11/23/2022, 8:00 PMDATASET_ENABLE_SCSI
- no idea what this is or what it does
• ENTITY_REGISTRY_CONFIG_PATH
- this is a yaml file in the container, does it need to be persisted across restarts or is it effectively a cache? if it needs to be persisted, should it be shared across all containers if running replicas?
• PE_CONSUMER_ENABLED
- i believe PE means platform events from my searching, but not quite sure what this enables/disables. is this the variable we set to false
when we are deploying MAE/MCE consumers separately?
• MAE_CONSUMER_ENABLED
- how does this work with PE_CONSUMER_ENABLED
? does it mean the MAE consumer should be started in GMS, and is not running separately?
• MCE_CONSUMER_ENABLED
- same question as above for MAE_CONSUMER_ENABLED
^
basically given a deployment with distinct containers for GMS, MAE consumer, and MCE consumer, should the three above variables all be false
? when GMS is running as a replicaset, do the replicas need the yaml file to persist like a daemonset would do, or can they rebuild the file on server boot if not present?shy-dog-84302
11/24/2022, 12:56 PMlimited-sundown-13355
11/25/2022, 4:52 AMhallowed-kilobyte-916
11/25/2022, 8:53 AMfailed to login. An unexpected error occured.
Upon digging around, i read that this error occurs when gms is unhealthy. Unfortunately when I check, it is indeed unhealthy. This is the log
https://gist.github.com/theSekyi/d0f379e53e6a86160f006d87afdf6b8fshy-dog-84302
11/25/2022, 11:30 AMlifecycle: map[postStart:map[exec:map[command:[/bin/sh -c echo "username:password" > /datahub-frontend/conf/user.props
]]]]
I believe this is because the lifecycle element is not properly indented in values.yaml file.
My values override looks like this:
lifecycle:
postStart:
exec:
command:
- /bin/sh
- -c
- |
echo "username:password" > /datahub-frontend/conf/user.props
Any clue what is going wrong here?strong-father-80629
11/25/2022, 7:47 PMred-waitress-53338
11/28/2022, 4:08 AMcurl <https://google-cloudrun-gms-service/config>
but it is not working when I do curl <https://google-cloudrun-gms-service:8080/config>
, so therefore I want to pass NULL as the DATAHUB_GMS_PORT value for the frontend application.
Any ideas please??famous-quill-82626
11/28/2022, 4:54 AMToken based authentication is currently disabled. Contact your DataHub administrator to enable this feature.
Instructions were to change the auth setting on the yaml file, to set metadata_service_authentication from false to true and then redeploy.
I solely made the following change in the file:
global:
...
metadata_service_authentication:
# enabled: false
enabled: true
systemClientId: "__datahub_system"
systemClientSecret:
...
.. however , now my pods for frontend and gms will not start:
NAMESPACE NAME READY STATUS RESTARTS AGE
datahub-local datahub-datahub-frontend-7c7bbd5d64-4fr99 0/1 CreateContainerConfigError 0 3m42s
datahub-local datahub-datahub-gms-5c5c549c7d-n6k88 0/1 CreateContainerConfigError 0 3m42s
datahub-local datahub-elasticsearch-setup-job-tkffw 0/1 Completed 0 6m15s
datahub-local datahub-kafka-setup-job-45scn 0/1 Completed 0 6m8s
datahub-local datahub-mysql-setup-job-stwhn 0/1 Completed 0 3m47s
datahub-local elasticsearch-master-0 1/1 Running 0 9m46s
datahub-local prerequisites-cp-schema-registry-b55968566-zf5lm 2/2 Running 0 9m46s
datahub-local prerequisites-kafka-0 1/1 Running 4 (6m58s ago) 9m46s
datahub-local prerequisites-mysql-0 1/1 Running 0 9m46s
datahub-local prerequisites-neo4j-community-0 1/1 Running 0 9m46s
datahub-local prerequisites-zookeeper-0 1/1 Running 0 9m46s
.. any help would be much appreciated
Peteclever-lamp-13963
11/28/2022, 9:58 AMdocker quickstart?
best-umbrella-88325
11/29/2022, 7:25 AMswift-wolf-62993
11/29/2022, 8:15 AM| Docker Image | Type | CRITICAL | HIGH | LOW | MEDIUM | UNKNOWN |
| ----------------------------------------- | ---------- | -------- | ---- | --- | ------ | ------- |
| acryldata/datahub-frontend-react:v0.9.2.4 | jar | 24 | 56 | 3 | 35 | 2 |
| acryldata/datahub-gms:v0.9.2.4 | gobinary | | 11 | | 2 | |
| | jar | 16 | 30 | 2 | 37 | 5 |
| acryldata/datahub-ingestion:v0.9.2.4 | debian | 17 | 378 | 614 | 306 | 3 |
| | gobinary | | 11 | | 2 | |
| | jar | 21 | 38 | 4 | 20 | 5 |
| | python-pkg | 3 | 12 | 1 | 11 | |
| acryldata/datahub-mae-consumer:v0.9.2.4 | gobinary | | 11 | | 2 | |
| | jar | 16 | 21 | 1 | 28 | 5 |
| acryldata/datahub-mce-consumer:v0.9.2.4 | gobinary | | 11 | | 2 | |
| | jar | 16 | 21 | 1 | 28 | 5 |
| | | 113 | 600 | 626 | 473 | 25 |
shy-dog-84302
11/29/2022, 10:08 PMdatahub-upgrade-job
while updating my datahub installation in k8s from helm charts from 0.2.96 -> 0.2.114
Error message and the upgrade-job yaml file attached in thread 🧵
Anyone has experienced similar issue with possible hints for solving it?witty-motorcycle-52108
11/30/2022, 5:40 PM