Error: No connection established #1064

apatora · 2019-10-04T08:02:20Z

Problem description

Since google-gax forced the grpc-js version to 0.6.4 (googleapis/gax-nodejs@628db9e), I am having the following issue :

Error: No connection established
    at Http2CallStream.call.on (/usr/src/node_modules/@google-cloud/bigtable/node_modules/@grpc/grpc-js/build/src/call.js:68:41)
    at Http2CallStream.emit (events.js:203:15)
    at Http2CallStream.EventEmitter.emit (domain.js:448:20)
    at process.nextTick (/usr/src/node_modules/@google-cloud/bigtable/node_modules/@grpc/grpc-js/build/src/call-stream.js:75:22)
    at process._tickCallback (internal/process/next_tick.js:61:11)

Reproduction steps

The bug only happens after one hour. We are using grpc-js inside @google-cloud/bigtable and our bigtable instance is autoscaling.

The text was updated successfully, but these errors were encountered:

alexander-fenster · 2019-10-04T16:01:15Z

Thank you for the report! Just to confirm, does that mean that the script should have an hour of idle time with no network requests to experience that, or just an hour of runtime?

harscoet · 2019-10-04T16:22:05Z

Similar issue on @google-cloud/[email protected]
After about 10 minutes of idle time with no network requests, any call to "publish" callbacks after 10 minutes (maxRetryDelayMillis) to say "Retry total timeout exceeded before any response was received"
To be able to find this error "No connection established", I had to add logs in the google-gax module

reichjustin · 2019-10-04T16:24:09Z

We are seeing the exact same issues as @harscoet with @google-cloud/[email protected]

apatora · 2019-10-04T16:24:35Z

It happens after an hour of runtime (I had this issue on our main API). Then it starts to throw those errors on separate processes progressively.

weipublic · 2019-10-04T16:41:00Z

Same issue when using @google-cloud/datastore which depends on google-gax

alexander-fenster · 2019-10-04T17:07:58Z

We are looking into this and will either fix it ASAP, or release an update to google-gax that pins @grpc/grpc-js to an older version.

murgatroid99 · 2019-10-04T17:33:12Z

Just to make sure I understand, are you making some requests that succeed, then going idle for a while, then making more requests and seeing these errors?

alexander-fenster · 2019-10-04T17:38:14Z

Also, do you folks run your code on a physical machine, or in any kind of cloud e.g. cloud functions?

reichjustin · 2019-10-04T17:42:15Z

@murgatroid99 we are seeing that our services are running fine for 10ish minutes and then we start dropping connections. At this time we see deadline exceeded errors. Once this happens we are unable to have successful requests with both google-cloud/pubsub and google-cloud/datastore

@alexander-fenster we are seeing this using with services running within GKE containers

weipublic · 2019-10-04T18:32:35Z

We downgraded @grpc/grpc-js to 0.5.4 and also other related google libraries to a version that don't depend on @grpc/[email protected]. The problem seems gone. It may related to #1062 & #1061

murgatroid99 · 2019-10-04T18:36:50Z

If my fix is right, this problem was actually in #1015 but it was overshadowed by other problems.

murgatroid99 · 2019-10-04T21:29:27Z

I have published version 0.6.5 of @grpc/grpc-js. You should pick it up if you update your dependencies. Please try that and see if it solves this problem.

alexander-fenster · 2019-10-05T00:04:07Z

@apatora @harscoet @reichjustin @weipublic Could you folks please check if the fix in v0.6.5 works for you all, and let us know? Thank you!

apatora · 2019-10-05T10:25:30Z

@alexander-fenster I tried v0.6.5 and I still have the issue. Lots of Error: No connection established after an hour of runtime.

Vinceveve · 2019-10-07T13:56:51Z

Same here, with DataStore and PubSub, 0.6.5 doesn't fix the issue

bendoran · 2019-10-07T14:53:28Z

Same issues for us when using @google-cloud/datastore which depends on google-gax

murgatroid99 · 2019-10-07T17:04:22Z

Can someone seeing this issue with grpc-js 0.6.5 run with the environment variables GRPC_TRACE=all and GRPC_VERBOSITY=DEBUG and share the log output? If you can't set environment variables the normal way you can set those on process.env before loading any libraries.

murgatroid99 · 2019-10-07T18:05:05Z

I would also like to understand how exactly this problem is manifesting. Are you seeing one or a few errors and then later calls succeed? Or do you see this error and then all subsequent calls fail with the same error? Or something else?

rvillane · 2019-10-07T19:37:00Z

would be reasonable to suggest using pinned @grpc/grpc-js versions ? just to avoid a large impact when those sensitive dependencies run into issues.

Meemaw · 2019-10-07T20:12:19Z

We have seen those errors starting to occur around 1 hour after a fresh pod creation. After those started, all subsequent calls were starting to fail. Pintpointing lib to previous working version (0.5.2) resolved the issue. (using google Firestore)

rvillane · 2019-10-07T20:54:33Z

I tried the trick suggested in #1027 and run npx npm-force-resolutions && npm install

  "resolutions": {
    "@grpc/grpc-js": "0.5.2",
    "google-gax": "1.6.2"
  }

however, I'm getting the following error:

Error: Cannot find module '@grpc/proto-loader'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/dist/node_modules/@google-cloud/pubsub/node_modules/google-gax/build/src/grpc.js:34:25)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/dist/node_modules/@google-cloud/pubsub/node_modules/google-gax/build/src/index.js:33:16)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/dist/node_modules/@google-cloud/pubsub/build/src/v1/publisher_client.js:18:13)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)

any ideas ?

My app also uses other google cloud dependencies

"dependencies": {
"@google-cloud/storage": "3.2.1",
"@google-cloud/trace-agent": "3.6.1",
"@google-cloud/pubsub": "0.32.1"
},

murgatroid99 · 2019-10-07T22:11:41Z

I have published 0.6.6 with another possible fix for this problem. If anyone is willing to try it out and report the result that would be helpful.

alexander-fenster · 2019-10-07T23:38:27Z

@rvillane We normally don't pin dependencies since it makes it much harder to release patches. I understand the frustration caused by these issues, we'll definitely go ahead and pin the version to some v0.5.x if the problem is not fixed soon enough.

[updated: it said "0.4.x" originally, 0.5.x should be fine though]

murgatroid99 · 2019-10-07T23:45:52Z

As far as I know there are no outstanding issues with 0.5.x

murgatroid99 · 2019-11-19T01:22:36Z

Again, it would be helpful to see the confirmation of which version(s) of the library you have, as well as the stack trace of the errors you are getting.

In addition to that, as mentioned previously in this issue it would be helpful to see the output of running your code with the environment variables GRPC_TRACE=all and GRPC_VERBOSITY=DEBUG, particularly the log lines around when the error occurs.

iShaymus · 2019-11-19T10:23:27Z

@murgatroid99 I will try. It becomes difficult since it is completely random if and when it happens.

iShaymus · 2019-11-19T10:27:37Z

While I try and get a stack trace. Here is the error from the functions log

Error: No connection established at Http2CallStream.call.on (/srv/node_modules/@grpc/grpc-js/build/src/call.js:68:41) at emitOne (events.js:121:20) at Http2CallStream.emit (events.js:211:7) at process.nextTick (/srv/node_modules/@grpc/grpc-js/build/src/call-stream.js:75:22) at _combinedTickCallback (internal/process/next_tick.js:132:7) at process._tickDomainCallback (internal/process/next_tick.js:219:9)

iShaymus · 2019-11-19T10:49:13Z

"google-gax": {
      "version": "1.9.0",
      "resolved": "https://registry.npmjs.org/google-gax/-/google-gax-1.9.0.tgz",
      "integrity": "sha512-15hBX53yafuCCOXCVdahNuDpza0YNiNgrWY0iohav+ZuAcmSPb8WNcCufgNmYUTLJxyFxpEFSm/OKWm8MQxkEQ==",
      "optional": true,
      "requires": {
        "@grpc/grpc-js": "0.6.9",
        "@grpc/proto-loader": "^0.5.1",
        "@types/long": "^4.0.0",
        "abort-controller": "^3.0.0",
        "duplexify": "^3.6.0",
        "google-auth-library": "^5.0.0",
        "is-stream-ended": "^0.1.4",
        "lodash.at": "^4.6.0",
        "lodash.has": "^4.5.2",
        "node-fetch": "^2.6.0",
        "protobufjs": "^6.8.8",
        "retry-request": "^4.0.0",
        "semver": "^6.0.0",
        "walkdir": "^0.4.0"
      },

iShaymus · 2019-11-19T10:50:57Z

"@grpc/grpc-js": {
      "version": "0.6.9",
      "resolved": "https://registry.npmjs.org/@grpc/grpc-js/-/grpc-js-0.6.9.tgz",
      "integrity": "sha512-r1nDOEEiYmAsVYBaS4DPPqdwPOXPw7YhVOnnpPdWhlNtKbYzPash6DqWTTza9gBiYMA5d2Wiq6HzrPqsRaP4yA==",
      "optional": true,
      "requires": {
        "semver": "^6.2.0"
      }

iShaymus · 2019-11-19T10:56:38Z

npm ls returns 0.6.9 as the only version . How do I add the environment variables you specified with my functions hosted on firebase itself

murgatroid99 · 2019-11-19T19:01:48Z

At the very beginning of your script, before imports, you can write process.env.GRPC_TRACE='all' and process.env.GRPC_VERBOSITY='DEBUG'.

kaushaldeck · 2019-11-20T12:01:00Z

I am facing this issue and I am using Firebase admin
{ Error: No connection established
at Http2CallStream.call.on (/Users/XXXXXX/node_modules/@grpc/grpc-js/build/src/call.js:68:41)
at Http2CallStream.emit (events.js:194:15)
at process.nextTick (/Users/XXXXX/Work/XXXXX/node_modules/@grpc/grpc-js/build/src/call-stream.js:75:22)
at process._tickCallback (internal/process/next_tick.js:61:11)
code: 14,
details: 'No connection established',

kaushaldeck · 2019-11-20T17:08:50Z

As mentioned above I am using Firebase and am getting the connection failure error. I added the proc.env settings and here is the log

2019-11-20T16:48:52.351Z | subchannel | 172.217.163.170:443 READY -> IDLE
2019-11-20T16:48:52.352Z | pick_first | Connect to address list 172.217.163.170:443
2019-11-20T16:48:52.353Z | pick_first | Start connecting to subchannel with address 172.217.163.170:443
2019-11-20T16:48:52.353Z | pick_first | READY -> CONNECTING
2019-11-20T16:48:52.353Z | resolving_load_balancer | firestore.googleapis.com:443 READY -> CONNECTING
2019-11-20T16:48:52.353Z | connectivity_state | firestore.googleapis.com:443 READY -> CONNECTING
2019-11-20T16:48:52.353Z | dns_resolver | Resolution update requested for target firestore.googleapis.com:443
2019-11-20T16:48:52.355Z | subchannel | 172.217.163.170:443 IDLE -> CONNECTING
2019-11-20T16:48:52.356Z | subchannel | 172.217.163.170:443 CONNECTING -> TRANSIENT_FAILURE
2019-11-20T16:48:52.403Z | dns_resolver | Resolved addresses for target firestore.googleapis.com:443: 172.217.163.170:443
2019-11-20T16:48:52.403Z | pick_first | Connect to address list 172.217.163.170:443
2019-11-20T16:48:52.403Z | pick_first | CONNECTING -> TRANSIENT_FAILURE
2019-11-20T16:48:52.403Z | resolving_load_balancer | firestore.googleapis.com:443 CONNECTING -> TRANSIENT_FAILURE
2019-11-20T16:48:52.403Z | connectivity_state | firestore.googleapis.com:443 CONNECTING -> TRANSIENT_FAILURE
2019-11-20T16:48:53.362Z | subchannel | 172.217.163.170:443 TRANSIENT_FAILURE -> IDLE

murgatroid99 · 2019-11-20T18:07:37Z

@kaushaldeck Can you also confirm what version of @grpc/grpc-js you are using?

kaushaldeck · 2019-11-21T06:41:03Z

Hope this helps

npm ls @grpc/grpc-js
[email protected] /Users/kaushalc/XXXX
└─┬ [email protected]
  └─┬ @google-cloud/[email protected]
    └─┬ [email protected]
      └── @grpc/[email protected]

murgatroid99 · 2019-11-21T17:36:05Z

Yes. That trace log shows a bug that was fixed in @grpc/grpc-js version 0.6.7. I suggest upgrading your dependencies so that you have at least version 0.6.9, and if you can't, I suggest filing an issue against firebase-admin.

ravi8x · 2019-12-22T06:06:15Z

I had this problem for few months. My issue is, the port 8080 is closed on my Mac. I opened the port and everything worked perfectly.

alexandrugheorghe · 2020-02-25T14:55:32Z

I'm experiencing sustained CPU spikes to 100% after an hour since a pod is started. I've created a debug pod which doesn't handle any traffic and it still manifests the same way. After profiling the CPU I've found that calls to startCallStream consistently fail which causes the whole tryPick function to be called again basically blocking the node process:

Is it intended for this code: https://github.com/grpc/grpc-node/pull/1251/files#diff-a96b991cf71efa63f54e0313d45cf39cR234-R257 to create a loop like the one I described?

I'm currently using these versions of google libraries:

    "@google-cloud/connect-datastore": "^4.0.0",
    "@google-cloud/datastore": "^5.0.6",
    "@google-cloud/firestore": "^3.5.1",
    "@google-cloud/pubsub": "^1.5.0",

The libraries are using "@grpc/[email protected]", "@grpc/grpc-js@^0.6.12"
I will update this post with logs from GRPC_TRACK in an hour or so.

murgatroid99 · 2020-02-25T16:42:01Z

@alexandrugheorghe That looks like the same bug as reported in googleapis/nodejs-pubsub#890, and that user says that the problem was fixed in @grpc/grpc-js version 0.6.18.

alexandrugheorghe · 2020-02-25T16:55:12Z

@murgatroid99 I'll update now and check it again in an hour.

alexandrugheorghe · 2020-02-26T11:22:00Z

@murgatroid99 Sorry for the late reply. Pods have been stable, version 0.6.18 has fixed my issues.
Thanks again for the quick reply and the fix.

tcarrio · 2020-06-05T15:50:52Z

I'm hoping this issue hasn't resurfaced, but I did encounter the same error in a project that had been idle for some time. I recycled the pod so I should have an idea of the timeout being the cause in the future, but it impacted all our instances in a test environment.

The error:

err:
    message: '14 UNAVAILABLE: No connection established'
    name: Error
    stack: >
        Error: 14 UNAVAILABLE: No connection established
            at Object.callErrorFromStatus (/app/packages/animus/node_modules/@grpc/grpc-js/src/call.ts:81:24)
            at Object.onReceiveStatus (/app/packages/animus/node_modules/@grpc/grpc-js/src/client.ts:334:36)
            at Object.onReceiveStatus (/app/packages/animus/node_modules/@grpc/grpc-js/src/client-interceptors.ts:434:34)
            at Object.onReceiveStatus (/app/packages/animus/node_modules/@grpc/grpc-js/src/client-interceptors.ts:397:48)
            at Http2CallStream.outputStatus (/app/packages/animus/node_modules/@grpc/grpc-js/src/call-stream.ts:230:22)
            at Http2CallStream.maybeOutputStatus (/app/packages/animus/node_modules/@grpc/grpc-js/src/call-stream.ts:280:14)
            at Http2CallStream.endCall (/app/packages/animus/node_modules/@grpc/grpc-js/src/call-stream.ts:263:12)
            at Http2CallStream.cancelWithStatus (/app/packages/animus/node_modules/@grpc/grpc-js/src/call-stream.ts:597:10)
            at ChannelImplementation.tryPick (/app/packages/animus/node_modules/@grpc/grpc-js/src/channel.ts:387:22)
            at ChannelImplementation._startCallStream (/app/packages/animus/node_modules/@grpc/grpc-js/src/channel.ts:433:10)
            at Http2CallStream.start (/app/packages/animus/node_modules/@grpc/grpc-js/src/call-stream.ts:573:18)
            at BaseUnaryInterceptingCall.start (/app/packages/animus/node_modules/@grpc/grpc-js/src/client-interceptors.ts:374:15)
            at BaseUnaryInterceptingCall.start (/app/packages/animus/node_modules/@grpc/grpc-js/src/client-interceptors.ts:437:11)
            at ServiceClientImpl.makeUnaryRequest (/app/packages/animus/node_modules/@grpc/grpc-js/src/client.ts:315:10)
            at ServiceClientImpl.<anonymous> (/app/packages/animus/node_modules/@grpc/grpc-js/src/make-client.ts:174:15)
            at args (/app/packages/animus/node_modules/dialogflow/src/v2beta1/sessions_client.js:175:35)
            at /app/packages/animus/node_modules/google-gax/src/normalCalls/timeout.ts:54:13
            at OngoingCallPromise.call (/app/packages/animus/node_modules/google-gax/src/call.ts:82:23)
            at NormalApiCaller.call (/app/packages/animus/node_modules/google-gax/src/normalCalls/normalApiCaller.ts:46:15)
            at funcPromise.then.then (/app/packages/animus/node_modules/google-gax/src/createApiCall.ts:103:26)
            at Object.dynatraceOnServiceExecutionIndicator [as doInvoke] (/opt/dynatrace/oneagent/agent/bin/1.195.54.20200529-113801/any/nodejs/nodejsagent.js:1803:20)
            at Object.a.safeInvoke (/opt/dynatrace/oneagent/agent/bin/1.195.54.20200529-113801/any/nodejs/nodejsagent.js:1854:29)
            at /opt/dynatrace/oneagent/agent/bin/1.195.54.20200529-113801/any/nodejs/nodejsagent.js:7079:25
            at process._tickCallback (internal/process/next_tick.js:68:7)"
    code: 14

We install dependencies from the package-lock.json, which has @grpc/grpc-js locked in at 1.0.4.

{
  // deps...
  "@grpc/grpc-js": {
    "version": "1.0.4",
    "resolved": "https://registry.npmjs.org/@grpc/grpc-js/-/grpc-js-1.0.4.tgz",
    "integrity": "sha512-Qawt6HUrEmljQMPWnLnIXpcjelmtIAydi3M9awiG02WWJ1CmIvFEx4IOC1EsWUWUlabOGksRbpfvoIeZKFTNXw==",
    "requires": {
      "google-auth-library": "^6.0.0",
      "semver": "^6.2.0"
    },
    "dependencies": { /** deps... */ }
  }
}

Will have another issue opened if this has resurfaced. I'll be back with more if it's an issue we come across again.

AkhilA4 · 2021-01-03T08:04:22Z

Hello everyone, I've been trying to create a secret in the GCP from running the GCP APIs from AWS lambda. I tried setting the environment variable at the run time like process.env.GOOGLE_APPLICATION_CREDENTIALS = '/tmp/serviceAccountCreds.json'; . The GCP API for secret manager was running fine till DEC 29th on my environment. But from then on the API is throwing below error

Error: 14 UNAVAILABLE: No connection established
    at Object.callErrorFromStatus (/home/akhil/onboard/node_modules/@grpc/grpc-js/src/call.ts:81:24)
    at Object.onReceiveStatus /home/akhil/onboard/node_modules/@grpc/grpc-js/src/client.ts:334:36)
    at Object.onReceiveStatus /home/akhil/onboard/node_modules/@grpc/grpc-js/src/client-interceptors.ts:434:34)
    at Object.onReceiveStatus (/home/akhil/onboard/node_modules/@grpc/grpc-js/src/client-interceptors.ts:397:48)
    at /home/akhil/onboard/node_modules/@grpc/grpc-js/src/call-stream.ts:237:24
    at processTicksAndRejections (internal/process/task_queues.js:79:11) {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} }

@grpc/grpc-js version installed is 1.1.8

{
"_from": "@grpc/grpc-js@~1.1.1",
"_id": "@grpc/[email protected]",
"_inBundle": false,
"_integrity": "sha1-KEXw/D0b+7FQ7Xp4p2vfQbEm02c=",
"_location": "/@grpc/grpc-js",
"_phantomChildren": {
  "@types/long": "4.0.1",
  "lodash.camelcase": "4.3.0",
  "long": "4.0.0",
  "protobufjs": "6.10.2",
  "yargs": "15.4.1"
},

The secrets manager's version is 3.2.3

 "dependencies": {
    "@google-cloud/secret-manager": "^3.2.3",
    "aws-sdk": "^2.445.0",
    "aws4": "^1.8.0",

sidd-kulk · 2021-01-04T04:31:55Z

I am facing the same issue again:
package.json:

"@google-cloud/pubsub": "^1.1.6",
    "@grpc/grpc-js": "^1.1.7",

package-lock.json

"@google-cloud/pubsub": {
      "version": "1.7.3",
      "resolved": "https://registry.npmjs.org/@google-cloud/pubsub/-/pubsub-1.7.3.tgz",
...
"@grpc/grpc-js": {
          "version": "1.0.5",
          "resolved": "https://registry.npmjs.org/@grpc/grpc-js/-/grpc-js-1.0.5.tgz",
          "integrity": "sha512-Hm+xOiqAhcpT9RYM8lc15dbQD7aQurM7ZU8ulmulepiPlN7iwBXXwP3vSBUimoFoApRqz7pSIisXU8pZaCB4og==",
          "requires": {
            "semver": "^6.2.0"
          }
        }

ducvu91 · 2021-01-04T11:54:35Z

@sidcool1234 i'm too.
I'm use dialogflow, it doesn't usually happen
"@google-cloud/storage": "^2.5.0",
"@google-cloud/vision": "^1.8.0",
"actions-on-google": "^1.8.0",
"body-parser": "^1.18.3",
"config": "^3.0.1",
"dialogflow": "^1.2.0",
"dialogflow-fulfillment": "^0.6.1",

AkhilA4 · 2021-01-07T07:26:51Z

@sidcool1234 , @ducvu91 did you guys find any work-around or still persisting with this issue ? Please let me know if you guys found any work-around.

ducvu91 · 2021-01-07T09:05:25Z

@AkhilA4 not yet, Sometimes it happens and it's random, there's no specific case so I can't find where the cause is.

AkhilA4 · 2021-01-07T09:55:35Z

OK @ducvu91. Since last week, I'm encountering this issue every time I run the createSecret GCP API. Will try to create a new issue to get some attention for the issue. Not sure what needs to be done from dev end if this gets encountered in production environment.

Ignacio1996 · 2021-03-18T23:11:06Z

I was getting this issue because I setup the Firestore emulator and wasn't turning it on. If you recently enabled the emulators, you have to start them with firebase emulators:start . Then you'll start getting the information from your local database.

maikelrobier · 2021-03-30T16:55:20Z

Seeing the same issue with "@google-cloud/scheduler": "^1.6.0":

Error: 14 UNAVAILABLE: No connection established
    at Object.callErrorFromStatus (/app/node_modules/@grpc/grpc-js/build/src/call.js:30:26)
    at Http2CallStream.<anonymous> (/app/node_modules/@grpc/grpc-js/build/src/client.js:96:33)
    at Http2CallStream.emit (events.js:327:22)
    at Http2CallStream.EventEmitter.emit (domain.js:467:12)
    at /app/node_modules/@grpc/grpc-js/build/src/call-stream.js:97:22
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
    at runNextTicks (internal/process/task_queues.js:62:3)
    at listOnTimeout (internal/timers.js:523:9)
    at processTimers (internal/timers.js:497:7)

UPDATE:

Not a frequent issue, it randomly happened today.
It was running on Node.js 12.
Resolved @grpc/grpc-js version was 0.6.15

After reading above I guess getting @grpc/grpc-js >= 0.6.18 could solve the issue 🤔

brachaIzakov · 2023-06-12T07:37:19Z

Hey
Trying to run simple pub/sub code in my code
Every time brings the following error:

Error: 1 CANCELED: Call cancelled
at callErrorFromStatus (C:\storage-actions\node_modules@grpc\grpc-js\build\src\call.js:31:19)
at Object.onReceiveStatus (C:\storage-actions\node_modules@grpc\grpc-js\build\src\client.js:192:76)
at Object.onReceiveStatus (C:\storage-actions\node_modules@grpc\grpc-js\build\src\client-interceptors.js:360:141)
at Object.onReceiveStatus (C:\storage-actions\node_modules@grpc\grpc-js\build\src\client-interceptors.js:323:181)
at C:\storage-actions\node_modules@grpc\grpc-js\build\src\resolving-call.js:94:78
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
for call at
{
code: 1,
details: 'Call cancelled',
metadata: Metadata { internalRepr: Map(0) {}, options: {} },
note: 'Exception occurred in retry method that was not classified as transient'
}

Is the problem related to a certain version and/or incompatible versions?

murgatroid99 mentioned this issue Oct 4, 2019

Pick first: go IDLE if all subchannels go IDLE #1066

Merged

murgatroid99 closed this as completed in #1066 Oct 4, 2019

murgatroid99 reopened this Oct 4, 2019

schmidt-sebastian mentioned this issue Oct 4, 2019

HUGE memory leak problem googleapis/nodejs-firestore#768

Closed

apatora mentioned this issue Oct 6, 2019

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. error #1027

Closed

alexander-fenster mentioned this issue Oct 7, 2019

runQuery() fails with timeout after some time of inactivity googleapis/nodejs-datastore#513

Closed

murgatroid99 closed this as completed Mar 31, 2020

yashmurty mentioned this issue Apr 27, 2020

[bug] Firebase dependency issue mamori-i-japan/mamori-i-japan-api#76

Open

AkhilA4 mentioned this issue Jan 4, 2021

Error: 14 UNAVAILABLE: No connection established googleapis/nodejs-secret-manager#198

Closed

Error: No connection established #1064

Error: No connection established #1064

Comments

apatora commented Oct 4, 2019

Problem description

Reproduction steps

alexander-fenster commented Oct 4, 2019

harscoet commented Oct 4, 2019

reichjustin commented Oct 4, 2019

apatora commented Oct 4, 2019

weipublic commented Oct 4, 2019

alexander-fenster commented Oct 4, 2019 • edited Loading

murgatroid99 commented Oct 4, 2019

alexander-fenster commented Oct 4, 2019

reichjustin commented Oct 4, 2019 • edited Loading

weipublic commented Oct 4, 2019

murgatroid99 commented Oct 4, 2019

murgatroid99 commented Oct 4, 2019

alexander-fenster commented Oct 5, 2019

apatora commented Oct 5, 2019

Vinceveve commented Oct 7, 2019

bendoran commented Oct 7, 2019

murgatroid99 commented Oct 7, 2019

murgatroid99 commented Oct 7, 2019

rvillane commented Oct 7, 2019

Meemaw commented Oct 7, 2019

rvillane commented Oct 7, 2019

murgatroid99 commented Oct 7, 2019

alexander-fenster commented Oct 7, 2019 • edited Loading

murgatroid99 commented Oct 7, 2019

murgatroid99 commented Nov 19, 2019

iShaymus commented Nov 19, 2019

iShaymus commented Nov 19, 2019

iShaymus commented Nov 19, 2019 • edited Loading

iShaymus commented Nov 19, 2019

iShaymus commented Nov 19, 2019 • edited Loading

murgatroid99 commented Nov 19, 2019

kaushaldeck commented Nov 20, 2019 • edited Loading

kaushaldeck commented Nov 20, 2019

murgatroid99 commented Nov 20, 2019

kaushaldeck commented Nov 21, 2019 • edited by murgatroid99 Loading

murgatroid99 commented Nov 21, 2019

ravi8x commented Dec 22, 2019

alexandrugheorghe commented Feb 25, 2020 • edited Loading

murgatroid99 commented Feb 25, 2020

alexandrugheorghe commented Feb 25, 2020

alexandrugheorghe commented Feb 26, 2020

tcarrio commented Jun 5, 2020

AkhilA4 commented Jan 3, 2021 • edited Loading

sidd-kulk commented Jan 4, 2021 • edited Loading

ducvu91 commented Jan 4, 2021

AkhilA4 commented Jan 7, 2021

ducvu91 commented Jan 7, 2021 • edited Loading

AkhilA4 commented Jan 7, 2021

Ignacio1996 commented Mar 18, 2021

maikelrobier commented Mar 30, 2021 • edited Loading

brachaIzakov commented Jun 12, 2023

alexander-fenster commented Oct 4, 2019 •

edited

Loading

reichjustin commented Oct 4, 2019 •

edited

Loading

alexander-fenster commented Oct 7, 2019 •

edited

Loading

iShaymus commented Nov 19, 2019 •

edited

Loading

iShaymus commented Nov 19, 2019 •

edited

Loading

kaushaldeck commented Nov 20, 2019 •

edited

Loading

kaushaldeck commented Nov 21, 2019 •

edited by murgatroid99

Loading

alexandrugheorghe commented Feb 25, 2020 •

edited

Loading

AkhilA4 commented Jan 3, 2021 •

edited

Loading

sidd-kulk commented Jan 4, 2021 •

edited

Loading

ducvu91 commented Jan 7, 2021 •

edited

Loading

maikelrobier commented Mar 30, 2021 •

edited

Loading