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.

Logging stops after gax timeout

See original GitHub issue

Environment details

- OS: Alpine latest: 3.9.4
- Node.js version: 12.12.0
- @google-cloud/logging-winston version: 2.1.0

Steps to reproduce

After using latest nodejs-logging-winston in 2.1.0 the logging to Stackdriver stops suddenly after a few hours of logging. A few minutes before it stops we see the following exception trace coming from google-gax:

Error: Retry total timeout exceeded before any response was received at repeat (/app/node_modules/google-gax/build/src/normalCalls/retries.js:80:31) at Timeout._onTimeout (/app/node_modules/google-gax/build/src/normalCalls/retries.js:113:25) at listOnTimeout (internal/timers.js:531:17) at processTimers (internal/timers.js:475:7)

After switching back to nodejs-logging-winston version 2.0.1 everything worked fine again. The google-gax message does not appear in 2.0.1 but immediately comes back if we switch forward to version 2.1.0

Any ideas?

Issue Analytics

State:
Created 4 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

2reactions

bcoecommented, Oct 24, 2019

@twskj sounds good 👍 5.5.3 should force you on to @grpc/grpc-js@0.6.9, if you continue to run into any issues, we can try running your deployment with:

GRPC_TRACE=all and GRPC_VERBOSITY=DEBUG

And I can loop someone in from grpc to dig into your problem specifically.

0reactions

soldaircommented, Nov 4, 2019

closing issue because the fix is in grpc-js. please reopen if i’m incorrect here