```usr/lib/python3/dist-packages/paramiko/transpor...
# troubleshoot
l
Copy code
usr/lib/python3/dist-packages/paramiko/transport.py:219: CryptographyDeprecationWarning: Blowfish has been deprecated
  "class": algorithms.Blowfish,
[2022-08-03 15:41:16,888] DEBUG    {datahub.telemetry.telemetry:202} - Sending init Telemetry
[2022-08-03 15:41:16,967] DEBUG    {datahub.telemetry.telemetry:235} - Sending Telemetry
[2022-08-03 15:41:17,013] INFO     {datahub.cli.ingest_cli:170} - DataHub CLI version: 0.8.41.2
[2022-08-03 15:41:17,027] DEBUG    {datahub.cli.ingest_cli:178} - Using config: {'source': {'type': 'delta-lake', 'config': {'base_path': '<s3://dt.datalake-dev/eventsData/us-west-1/>', 's3': {'aws_config': {'aws_access_key_id': 'foo', 'aws_secret_access_key': 'bar'}}}}, 'sink': {'type': 'datahub-rest', 'config': {'server': '<http://localhost:8080>'}}}
[2022-08-03 15:41:17,121] DEBUG    {datahub.ingestion.sink.datahub_rest:69} - Setting env variables to override config
[2022-08-03 15:41:17,121] DEBUG    {datahub.ingestion.sink.datahub_rest:71} - Setting gms config
[2022-08-03 15:41:17,122] DEBUG    {datahub.ingestion.run.pipeline:162} - Sink type:datahub-rest,<class 'datahub.ingestion.sink.datahub_rest.DatahubRestSink'> configured
[2022-08-03 15:41:17,122] INFO     {datahub.ingestion.run.pipeline:163} - Sink configured successfully. DataHubRestEmitter: configured to talk to <http://localhost:8080>
[2022-08-03 15:41:17,618] ERROR    {logger:39} - Deequ is still not supported in spark version: spark-3.0.2
[2022-08-03 15:41:17,618] INFO     {logger:40} - Using deequ: com.amazon.deequ:deequ:1.2.2-spark-3.0
[2022-08-03 15:41:17,820] ERROR    {datahub.ingestion.run.pipeline:127} - 's3'
[2022-08-03 15:41:17,821] INFO     {datahub.cli.ingest_cli:119} - Starting metadata ingestion
[2022-08-03 15:41:17,821] INFO     {datahub.cli.ingest_cli:137} - Finished metadata ingestion

Failed to configure source (delta-lake) due to 's3'
c
You can ignore the spark thing safely here. Main issue is config file is not configured correctly. To avoid s3 config related issues, you can either setup environment variable or credentials file based aws authentication. Or please share your config file here to look for issues.