-
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
systemd collector hangs and opens a lot of dbus connections #1535
Comments
Have similar issue. Had to disable systemd collector
|
Well somebody still needs to figure out if this is the node-exporter or dbus acting up. |
@DonatasFe what was your RHEL version? |
Yeah let us know, if it’s solved in more recent version I think it can be closed |
|
I actually meant, the version of your redhat install. |
Here it is: CentOS Linux release 7.4.1708 (Core) |
Going to assume this is fixed in newer versions. |
I just had this issue on CentOS 7.5 with node_exporter 1.1.2. Restarting systemd with |
Host operating system: output of
uname -a
Linux xxxx 3.10.0-957.10.1.el7.x86_64 #1 SMP Thu Feb 7 07:12:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of
node_exporter --version
node_exporter, version 0.18.1 (branch: HEAD, revision: 3db7773)
build user: root@b50852a1acba
build date: 20190604-16:41:18
go version: go1.12.5
node_exporter command line flags
--collector.systemd
Are you running node_exporter in Docker?
No
What did you do that produced an error?
Retrieve systemd metrics on a system where the dbus/systemd-logind got stuck for some reason.
What did you expect to see?
In the previous version (0.17.0) the exporter returned the other metrics, even though something was wrong with getting systemd metrics.
What did you see instead?
In version 0.18.1 the behavior changed and the exporter just hangs, never returning anything.
Restarting the 2 services (dbus and systemd-logind) makes it return immediately en spits out this on the console:
During such events where something goes wrong with systemd, there are also a lot of conenctions from node_exporter to the bus:
I'm not sure yet if node_exporter is causing dbus/systemd to misbehave or that it's a symptom of it.
Anyway, I think unresponsive connections are not closed properly before opening a new one. Causing a pile up of stale connections.
The text was updated successfully, but these errors were encountered: