-
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
cpu collector failed after 0.000248s: more CPU's than MAXCPU? #339
Comments
The code for this error comes from cpu_freebsd.go. I guess there must be something wrong with the way BSD cpu is retrieved. |
Yes, it seems that MAXCPU in const maxCPUTimesLen = C.MAXCPU * C.CPUSTATES is always 1. So this collector works on a single vm with 1 cpu / 1 core, but will never work on a multicore system. |
Here is a snippet how to get the number of cpus on various OSes: http://stackoverflow.com/questions/150355/programmatically-find-the-number-of-cores-on-a-machine |
This should be fixed now that the collector is replaced by a pure Go version. |
Just to confirm - I built this and am running it on my FreeNAS box and it's working just fine. I wrote up what I did here: https://blog.yo61.com/installing-prometheus-node_exporter-on-freenas/ |
Awesome! And great article, that should help me setting up some VM based tests too! |
Will this get pushed to the FreeBSD repos? I just installed from the latest repo for FreeBSD 10 amd64 and I'm still seeing this issue. |
@reverson You still see the issues with the 0.14-rc1 release? https://github.com/prometheus/node_exporter/releases/tag/v0.14.0-rc.1 |
Ah, I have not tried 0.14-rc1 as I was just using the version from the
FreeBSD official repo (on pfsense). I'll wait for 0.14.0 to be released.
Thanks @discordianfish
…On Sun, Feb 26, 2017 at 2:52 AM discordianfish ***@***.***> wrote:
@reverson <https://github.com/reverson> You still see the issues with the
0.14-rc1 release?
https://github.com/prometheus/node_exporter/releases/tag/v0.14.0-rc.1
The final 0.14.0 isn't released yet. See #441
<#441> for status on the
next rc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#339 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAX4YPH_Cy7W_5MXPc4vtwYMiC5qfJ9rks5rgVlZgaJpZM4Kwvbc>
.
|
…theus#339) * Fix for mountstats error due to multiline "impl_id" on FreeNAS This commit fixes an error happening when trying to parse data from FreeNAS NFS mount point. "impl_id" is printed in multiple lines, which triggers "not enough information for NFS stats" error. Signed-off-by: Jakub Wesolowski <jakubwesolowski@posteo.net>
I'm trying to get node_exporter running on a FreeNAS box, which is based on FreeBSD 10.3 STABLE.
I did this:
This works, but I see this error from the node_exporter regularly:
Any idea why I see this?
R.
The text was updated successfully, but these errors were encountered: