Error resolving cluster hostname

MongoDB Atlas
1

After making a new deployment (import via CLI) to Stitch / Realm, we have been receiving the following error message:

image
(sorry for the bad crop: translates to -> error resolving cluster hostname)

We have not been able to revert back or make the App work anymore, even with a --strategy replace on a working version.

Has anyone experienced a similar issue / knows how to resolve it?

Thanks!
Martin

2

The full error message: FunctionError: this service was recently updated, so it may take several minutes until the cluster can be connected to. Error: error resolving cluster hostname.

In the function, we try and get the service as follows: context.services.get(“database”).db(db_name);

It does not resolve itself after waiting even a couple of hours.

3

Same here from my functions after CLI update

ran on Thu Jul 30 2020 12:04:24 GMT+0200 (heure d’été d’Europe centrale)
took 301.4469ms
error:
this service was recently updated, so it may take several minutes until the cluster can be connected to. Error: error resolving cluster hostname
trace:
FunctionError: this service was recently updated, so it may take several minutes until the cluster can be connected to.

Error: error resolving cluster hostname
    at get (<native code>)
    at apply (<native code>)
    at <anonymous>:16:10
    at _callee$ (function.js:2:3)
    at call (<native code>)
    at tryCatch (<anonymous>:55:37)
    at invoke (<anonymous>:281:22)
    at <anonymous>:107:16
    at call (<native code>)
    at tryCatch (<anonymous>:55:37)
    at invoke (<anonymous>:145:20)
    at <anonymous>:180:11
    at <anonymous>:3:6
    at callInvokeWithMethodAndArg (<unknown>)
    at enqueue (<anonymous>:202:13)
    at <anonymous>:107:16
    at <anonymous>:226:9
    at _callee (function.js:1:11)
    at apply (<native code>)
    at function_wrapper.js:1:11
    at <anonymous>:12:1
4

“StitchServiceError: this service was recently updated, so it may take several minutes until the cluster can be connected to. Error: error resolving cluster hostname”

After updating from CLI

5

Hi,
I resolved this problem by deleting and recreating cluster link via realm web interface.

6

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.