-
Notifications
You must be signed in to change notification settings - Fork 36
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
Failed to obtain reader in the logs #331
Comments
What is the context of that error? Is that from staging? Your installation? which version? Is that after performing some action, or on startup? |
staging. the version is master. Because the error doesn't contain any info besides above I don't know when exactly it happens. Context around says during fetching events but looks like it doesn't happen always. the PR should help to debug it. |
Don't see this error on staging anymore (not exactly this but the one related to logging a function). Let's wait few days if there is still no error we can close it as "can't reproduce". It's possible that error was fixed in some previous commit (apparently lookout was deploying on different cluster since some days ago) |
Still nothing related in logs on new staging. |
I see this error in staging logs again:
not sure why new logrus version doesn't provide correct logs for this error. We need to investigate. |
When I try to reproduce it locally adding function with the same signature into logs I get:
|
Most probably it happens because we pass pointer to a function as a log field somewhere 😱 Here is a proposal to fix it in logrus: sirupsen/logrus#642 (comment) |
this error isn't formatted as json, so I guess the error happens during logging.
The text was updated successfully, but these errors were encountered: