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

stoped working yesterday from kubernetes engine #68

Closed
nabulaer opened this issue Feb 12, 2018 · 5 comments
Closed

stoped working yesterday from kubernetes engine #68

nabulaer opened this issue Feb 12, 2018 · 5 comments
Assignees
Labels
api: logging Issues related to the googleapis/nodejs-logging API. 🚨 This issue needs some love. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@nabulaer
Copy link

Environment details

  • OS: linux
  • Node.js version: 6.10.3
  • npm version:
  • @google-cloud/logging version: 1.1.2 , 1.1.3

Steps to reproduce

running the sample code from google docs. on local dev it works. on K8 it stopped yesterday. it did work until now. when I connect to the pod and run the code , the promise that return from log.write() is never resolved. no errors are going to the logs on gcp console. the stdout is going to the logs from nodejs. so the pod has access but not from the nodejs module

since promise is not resolved memory is growing all the time.

Thanks!

@nabulaer
Copy link
Author

I did not think it is related to issue #53 since it worked for me on 1.1.2 for the past weeks. but I have tried reverting to 1.1.1 and now logging works. so maybe it is related.

@nmathon
Copy link

nmathon commented Feb 23, 2018

+1
I can reproduce exactly the same problem. It's working with 1.1.1 but not with 1.1.2

@stephenplusplus
Copy link
Contributor

I've been able to reproduce, and I'm taking a look at it. Sorry for the delay.

@stephenplusplus stephenplusplus added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Mar 7, 2018
@ghost ghost removed the priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. label Mar 7, 2018
@stephenplusplus stephenplusplus mentioned this issue Mar 7, 2018
@stephenplusplus
Copy link
Contributor

I believe the fix has just been released under 1.1.5. Please try it out and let me know how it goes!

nabulaer added a commit to nabulaer/log4js-node-stackdriver that referenced this issue Mar 13, 2018
@nabulaer
Copy link
Author

tested with version 1.1.7 so far it is working.

@google-cloud-label-sync google-cloud-label-sync bot added the api: logging Issues related to the googleapis/nodejs-logging API. label Jan 31, 2020
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: logging Issues related to the googleapis/nodejs-logging API. 🚨 This issue needs some love. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

4 participants