-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 with DBus #242
Comments
Still happens from time to time. I expect it to be solved on OS restart (it's only with one specific instance); however we can't afford to reboot it just for this. |
We're running into this bug constantly (happens at least every couple days) on our nodes. We're on Debian 8. Any news on this bug ? |
No news yet - any debugging help welcome. |
godbus/dbus#45 looks lilke it's the same bug ? It appears to be fixed in a later version of godbus than what is vendored with node_exporter. I think I'll try to build a version of node_exporter with godbus updated and report back if it fixes the problem. |
Hello, so I forgot to report back. I did build a version with the latest godbus and it worked great since then, no panics to report. I'm reporting back now because we're upgrading to 0.13.0 and I saw godbus isn't updated. It's not a big deal but any chance the next version will use an updated godbus ? Thanks. |
PR to update vendoring (might as well catch them all). #372 |
#372 merged, I'll be starting a new release in January after a few more PRs get cleaned up and merged. |
Given that #372 is merged, I'd consider this fixed and close the issue. |
procfs: tidy up NetUnix APIs and internals
Since we activated systemd collector, it's the second time (four days after the first one) the exporter fails with
panic
, twice on the same host:We use the Debian-packaged exporter.
Starting again the exporter solves it.
The text was updated successfully, but these errors were encountered: