Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: 14 UNAVAILABLE: read ECONNRESET #2636

Open
vasu-rangpariya-yudiz opened this issue Dec 22, 2023 · 1 comment
Open

Error: 14 UNAVAILABLE: read ECONNRESET #2636

vasu-rangpariya-yudiz opened this issue Dec 22, 2023 · 1 comment

Comments

@vasu-rangpariya-yudiz
Copy link

Problem description

When I am trying to call a grpc request from a grpc client it works well for nearly 30-40 mins but after that time it automatically throws an error about the backend being unavailable although grpc server backend is running fine. after 2-3 failed requests It will automatically reconnect the grpc server and the same case happens again and again

Reproduction steps

Create a grpc server, a client with a docker image of 20-alpine and add corn that automatically calls one rest API and that rest API calls the grpc server after 30 minutes it gives a connection error

Environment

  • Linux, 5.10.199-190.747.amzn2.x86_64
  • Node v20 with Kubernetes with AWS ALB
  • @grpc/grpc-js, v1.9.13 [e.g. gRPC@1.12.0]
@murgatroid99
Copy link
Member

It would help to get client trace logs of one of these errors. Trace logging can be enabled by setting the environment variables GRPC_TRACE=all and GRPC_VERBOSITY=DEBUG. If you want to redirect the logging output you can use grpc.setLogger.

Specifically, it would help to see continuous logs starting with a request that succeeds, and then a request that fails with this error, and then another request that succeeds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants