-
Notifications
You must be signed in to change notification settings - Fork 12
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
panic: runtime error: invalid memory address or nil pointer dereference in serviceQuotaFetcher #205
Comments
Hello, I had a look but sadly can't reproduce the issue in my local environment. I also checked the logs of our current deployment (in case we missed something) but couldn't find a similar error. It looks like it received an unexpected value. Would you be able to run
...when you receive this error and share with us the values of the following codes: L-7B6409FD // DB instances
L-7ADDB58A // Total storage for all DB instances
L-272F1212 // Manual DB instance snapshots |
This commit is updating the exporter and servicequotas packages to properly pass the logger. In the `serviceQuotaFetcher` struct we have defined a logger field but it was never initialized. Which means any call to s.logger was panicking in the `serviceQuotaFetcher` methods. Properly passing the logger and storing it in the structure will allow us to properly use `s.logger` inside the `serviceQuotaFetcher` methods. This change has been made following this [issue][1] [1]: qonto#205
This commit is updating the exporter and servicequotas packages to properly pass the logger. In the `serviceQuotaFetcher` struct we have defined a logger field but it was never initialized. Which means any call to s.logger was panicking in the `serviceQuotaFetcher` methods. Properly passing the logger and storing it in the structure will allow us to properly use `s.logger` inside the `serviceQuotaFetcher` methods. This change has been made following this [issue][1] [1]: qonto#205
This commit is updating the exporter and servicequotas packages to properly pass the logger. In the `serviceQuotaFetcher` struct we have defined a logger field but it was never initialized. Which means any call to s.logger was panicking in the `serviceQuotaFetcher` methods. Properly passing the logger and storing it in the structure will allow us to properly use `s.logger` inside the `serviceQuotaFetcher` methods. This change has been made following this [issue][1] [1]: qonto#205 Signed-off-by: Clovis Delarue <[email protected]>
Hi, A new version 0.10.1 has been released to fix this panic 🙏 You probably have an other issue as this panic was happening if |
We are running
v0.10.0
in EKS on Amazon Linux 2 nodes and the exporter is crashing from time to time with the following error onserviceQuotaFetcher
:The exporter is configured with:
The text was updated successfully, but these errors were encountered: