question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

onConnectionError is not called for workers

See original GitHub issue

Hello!

We are facing some errors on the workers side, but the onConnectionError() never gets called. For example:

15:56:47.739 | zeebe |  [http] INFO: Grpc Stream Error: 1 CANCELLED: Received http2 header with status: 502
15:56:52.541 | zeebe |  [eval] INFO: The gateway returned HTTP Error 503 (Bad Gateway). This can be a transient failure while a Kubernetes node in Camunda Cloud is being pre-empted.
07:51:16.276 | zeebe |  [http] INFO: Stalled on Grpc Error
07:51:16.281 | zeebe |  [http] INFO: Grpc Stream Error: 14 UNAVAILABLE: TCP Read failed
09:49:54.840 | zeebe |  [eval] INFO: Stalled on Grpc Error
09:49:54.840 | zeebe |  [eval] INFO: Grpc Stream Error: 14 UNAVAILABLE: failed to connect to all addresses
10:05:03.134 | zeebe |  [http] INFO: Stalled on Grpc Error
10:05:03.134 | zeebe |  [http] INFO: Grpc Stream Error: 14 UNAVAILABLE: GOAWAY received

Also when we create a workflow instance the workers continue to work despite those errors, so I suppose these errors shouldn’t affect us right? We use latest version of library (0.24).

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
denissabramovscommented, Oct 13, 2020
  worker.on('ready', () => {
    console.log('worker is ready!');
  });

is working for me

1reaction
ellik95commented, Oct 1, 2020

The onReady() doesn’t get called as well if this helps.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Zeebe-node fails to connect if broker loaded after worker
I did get the GRPC errors in the client's log though, but no call to 'onConnectionError' (2) My worker microservice is built “FROM...
Read more >
Spring Apache Kafka onFailure Callback of KafkaTemplate ...
The thing now is: I'm expecting the "onFailure()" method to get called when the message could not be sent. But this seems not...
Read more >
zeebe-node - npm
onConnectionError : () => console.log(`Worker disconnected!`) }) These handlers are called whenever the gRPC channel is established or lost.
Read more >
Strange behaviour on a 64 bit system - PI Square - OSIsoft
Jan van der Ven (Customer) asked a question. ... "Exception in OnConnection Error HRESULT EFAIL has been returned from a call to a...
Read more >
REST request error handling on connection error
When I turn off my internet connection node fails. I'm not saying it's not possible but might be that different (development) approach is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found