Unable to run the landing task to land data on to snowflake

[akaradhya]

Hi Team,

We have setup Qlik Gateway on our Linux server. As part of testing the entire data flow we are moving data from MySql on to Snowflake.

As part of this, we have installed both the MySql and snowflake driver on the gateway machine. 

On QCDI, we are able to load the select tables from MySql but when we run the landing task, we are encountering the below error. Looked up online for this error and tried out of a few different workarounds, but was not able to resolve this issue. Below is the error that we are facing. Reaching out to the community to throw some light on this. 

Error Message: 

00021296: 2023-04-03T19:49:01 [METADATA_MANAGE ]E: RetCode: SQL_ERROR SqlState: HY000 NativeError: 4 Message: [Snowflake][Snowflake] (4) REST request for URL https://hy81676.ap-south-1.aws.snowflakecomputing.com:443/session/v1/login-request?requestId=b24c510... failed: CURLerror (curl_easy_perform() failed) - code=77 msg='Problem with the SSL CA cert (path? access rights?)' osCode=32 osMsg='Broken pipe'. [1022502] (ar_odbc_conn.c:584)00021296: 2023-04-03T19:49:01 [METADATA_MANAGE ]E: Cannot connect to Cloud server [1022502] (cloud_imp.c:3929)00021296: 2023-04-03T19:49:01 [METADATA_MANAGE ]E: Failed while preparing stream component 'EP_dQlG4yXlFTy7Vwr1BAgQDw'. [1022502] (metadatamanager.c:855)00021296: 2023-04-03T19:49:01 [METADATA_MANAGE ]E: Cannot create the target utility component [1022502] (metadatamanager.c:760)00021296: 2023-04-03T19:49:01 [TASK_MANAGER ]E: Creating Metadata Manager's utility components failed [1022502] (replicationtask.c:3875)00021296: 2023-04-03T19:49:01 [TASK_MANAGER ]W: Task 'TASK_bXvbR9NgDuoIzEJygk589w' encountered a recoverable error (repository.c:5919)

Thanks!

[CF_Debarati]

Hi @akaradhya ,

Please provide the following information:

1.  Linux version for the gateway.

 2. What version of MySQL and Snowflake driver you have installed. 

 3. Please attach the log where you see the error message.

[akaradhya]

Hi @CF_Debarati 
Pl find the requested information, 

1. CentOS Linux release 7.9.2009

2.  mysql connector -8.0.25 & Snowflake connector - 2.24.0

3. Attached the error log. 

[CF_Debarati]

Hi @akaradhya ,

Thank you for the information.

As per the User Guide for MySQL, https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/SourcesC...  

Only these driver versions are supported:

• 5.3.11 to 5.3.13
• 8.0.23
  
  Please try with MySQL 8.0.23 and let us know if the issue still persists.

[akaradhya]

Hi @CF_Debarati 

My bad on the communication front. We actually have MySQL 8.0.23 installed and not 8.0.25. And for snowflake we area on 2.24. The issue still persists. Kindly advise. 

[suresh_pulagam]

@akaradhya  You can run the below command on the gateway server and share the output. 

curl -v https://hy81676.ap-south-1.aws.snowflakecomputing.com

[suresh_pulagam]

@akaradhya  You can run the below query from the gateway server and share the output.

curl -v https://hy81676.ap-south-1.aws.snowflakecomputing.com

[fmarvnnt]

I think CentOS Linux release 7.9.2009 is not supported:  https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-prer... .

What is the position of Official Support?

Regards,

FMa

[CF_Debarati]

Officially as per the document, https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-prer...  

Data Movement gateway is certified for installation on Red Hat 8.x (64-bit). Although Data Movement gateway is certified on Red Hat, it is also supported on corresponding and compatible Linux distributions.

[akaradhya]

Hi @suresh_pulagam . Apologies on the delay. Below is the response on running the command. 

[root@vmi1229487 ~]# curl -v https://hy81676.ap-south-1.aws.snowflakecomputing.com
* About to connect() to hy81676.ap-south-1.aws.snowflakecomputing.com port 443 (#0)
* Trying 15.206.152.15...
* Connected to hy81676.ap-south-1.aws.snowflakecomputing.com (15.206.152.15) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* subject: CN=*.ap-south-1.snowflakecomputing.com
* start date: Mar 13 00:00:00 2023 GMT
* expire date: Apr 10 23:59:59 2024 GMT
* common name: *.ap-south-1.snowflakecomputing.com
* issuer: CN=Amazon RSA 2048 M02,O=Amazon,C=US
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: hy81676.ap-south-1.aws.snowflakecomputing.com
> Accept: */*
>
< HTTP/1.1 302 Found
< Date: Tue, 18 Apr 2023 13:32:07 GMT
< Expect-CT: enforce, max-age=3600
< Location: /console
< Strict-Transport-Security: max-age=31536000
< X-Content-Type-Options: nosniff
< X-Country: Turkey
< X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
< Content-Length: 0
< Connection: keep-alive