-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
cpufreq collector panic on hosts with offline cpus #2746
Comments
Ugh I thought we fixed this in prometheus/procfs#497 |
@taherkk any ideas if this is same/different from what you worked on? |
It looks like it was really fixed in prometheus/procfs#534, which was included in procfs v0.11.0. The stacktrace shows that node_exporter 1.6.0 was built with procfs v0.10.0. |
Ahh, boo, I should have pulled that into 1.6.1 today. |
Having the same problem.
|
@SuperQ when can we expect a release with latest procfs? |
hi, i find new BUG; ` goroutine 74 [running]: |
@SuperQ Guess this deserves a new release? |
Reverting to 1.5.0 stops this issue! I hope we can get an updated version soon too! |
+1 |
I would appreciate a new release as well! |
What are the criteria for a new release @discordianfish? I hope it's not too much trouble to get one sometime soon. Thank you very much for your hard work. |
We do not have a strict release schedule. But I am planning to do one soon. |
Looks like the problem fixed in https://github.com/prometheus/node_exporter/releases/tag/v1.7.0 and this issue can be closed |
Host operating system: output of
uname -a
node_exporter version: output of
node_exporter --version
node_exporter command line flags
node_exporter log output
Are you running node_exporter in Docker?
No. Systemd.
What did you do that produced an error?
Only occurs on hosts with offline CPU, in this case 96 vCPU down to 48 with SMT disabled.
Am able to avoid this issue by adding
--no-collector.cpufreq
to startup options.What did you expect to see?
No exit
What did you see instead?
Exit
The text was updated successfully, but these errors were encountered: