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

StackdriverExporter with application default credentials crashes #304

Closed
ocervell opened this issue Sep 10, 2018 · 4 comments
Closed

StackdriverExporter with application default credentials crashes #304

ocervell opened this issue Sep 10, 2018 · 4 comments

Comments

@ocervell
Copy link
Contributor

ocervell commented Sep 10, 2018

I noticed that currently, if we're using the application default credentials, the StackdriverExporter ends up crashing because of this issue in google-auth-library-python and the only way to make it work again is to restart the background thread.

The tracing collection goes fine for a while, and then starts failing in loops with:

...
  File "/usr/local/lib/python2.7/dist-packages/google/cloud/client.py", line 212, in __init__
    Client.__init__(self, credentials=credentials, _http=_http)
  File "/usr/local/lib/python2.7/dist-packages/google/cloud/client.py", line 125, in __init__
    credentials, _ = google.auth.default()
  File "/usr/local/lib/python2.7/dist-packages/google/auth/_default.py", line 286, in default
    raise exceptions.DefaultCredentialsError(_HELP_MESSAGE)
DefaultCredentialsError: Could not automatically determine credentials. Please set GOOGLE_APPLICATION_CREDENTIALS or
explicitly create credential and re-run the application. For more
information, please see
https://developers.google.com/accounts/docs/application-default-credentials.
@odeke-em
Copy link
Member

@ocervell thank you for filing this issue. I see you mailed out PR #291 which was merged. Is this issue still a problem?

Kindly paging @liyanhui1228 @c24t @mayurkale22 too

@ocervell
Copy link
Contributor Author

ocervell commented Nov 9, 2018

I haven't seen this for a while, not sure if still a problem. My PR #291 was unrelated I believe.

@c24t
Copy link
Member

c24t commented Nov 12, 2018

It doesn't look like it's fixed in the auth library, and I don't see any changes in the exporter or transport that would have fixed this since you opened the ticket. That said, I haven't run into this issue yet using app default credentials in e.g. the demo app.

If you have steps to reproduce it or a full stack trace we can try restarting the background thread on known errors like this, but it may be worth trying to fix the issue in the auth library instead.

@songy23
Copy link
Contributor

songy23 commented Jan 22, 2019

Not reproducible - see previous comments.

@songy23 songy23 closed this as completed Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants