Error with Snowflake Data Source since 2024-12-18 (Dremio-Cloud, EU, Azure)

1

I am seeing the following error in Dremio-Cloud in the EU control plane. I think it started yesterday (2024-12-18) around 3pm Pacific Time.

All queries going from Dremio to our Snowflake Data Source are failing with an error of “INTERNAL: Hostname is not a domain address, nor a correct ip address”.

Clicking to update or save the Snowflake Data Source configs results in a nondescript “Uknown Error”.

This error came up when I refreshed the Data Source Configs page. It’s the most descriptive I have encountered.

SYSTEM ERROR: StatusRuntimeException: INTERNAL: Hostname is not a domain address, nor a correct ip address [Error Id: 6eb1dfae-77dc-47c1-bd1a-e440ba84bff5 on 10.0.0.4:-1] (io.grpc.StatusRuntimeException) INTERNAL: Hostname is not a domain address, nor a correct ip address io.grpc.Status.asRuntimeException():532 io.grpc.protobuf.StatusProto.toStatusRuntimeException():52 com.dremio.common.exceptions.GrpcExceptionUtil.toStatusRuntimeException():105 com.dremio.common.exceptions.GrpcExceptionUtil.toStatusRuntimeException():92 com.dremio.common.exceptions.GrpcExceptionUtil.fallbackHandleException():126 com.dremio.common.exceptions.GrpcExceptionUtil.fallbackHandleException():179 com.dremio.exec.store.common.fetcher.SchemaFetcherServiceImpl.lambda$submitUnaryCall$13():375 com.dremio.context.RequestContext.run():103 com.dremio.common.concurrent.ContextMigratingExecutorService.lambda$decorate$4():246 java.util.concurrent.ThreadPoolExecutor.runWorker():1128 java.util.concurrent.ThreadPoolExecutor$Worker.run():628 java.lang.Thread.run():829

2

Thanks Capnjosh, Was this source working previously or is it a new source that you are configuring?

3

It was working fine up until yesterday.

When I tried creating a new Snowflake Data Source just now, I got the same error.

Also, when I tried to delete the Snowfalke Data Source, I got this error:

There was an error removing the source.Show less
Unknown error. Please contact Dremio Cloud support.

I have a chat thread going with “Hope” inside the Dremio-Cloud console, in case that’s relevant.

4

Great! You are in good hands then if you are talking with Hope. I confirmed that she and the team are looking into it. I would continue working with her for a resolution to this issue.

5

This issue has been resolved through chat, but adding the resolution here to close the loop.

The Host name field in your source settings needs to be strictly the hostname and nothing else

For example: if your hostname is “https://host.example.com”, you should instead use “host.example.com”

or, if you have additional parameters, such as “host.example.com?useSSL=true” you need to change it to “host.example.com”

1 Like
6

The issue was that the Dremio update yesterday started to enforce strict hostnames for the “Host” field of (at least) the Snowflake Data Source. We had “https://” in that Host value, so after yesterday’s update, it was no longer valid.

So that stack trace I provided did indicate the problem, though I didn’t think to try changing the Host value that had been working prior to yesterday.

Looks like all is fine in Dremio-Cloud land now :slight_smile:

2 Likes
7

Thank you for reaching out @capnjosh. Glad this was resolved so quickly.