-
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
node-exporter 0.15 fail on kernel 2.6.18 (RHEL5.5) #691
Comments
Go requires atleast 2.6.23 and does not support RHEL 5 and derivatives. |
It appears that this isn't a node_exporter or even a Go problem: https://www.linuxquestions.org/questions/slackware-14/fatal-kernel-too-old-935165/. |
Closing, as this is not an actionable issue for node_exporter. |
working like charm on 0.14 version of node-exporter |
This may be due to older versions of Go used to build previous releases. You may try building your own custom binary with an older Go compiler, but this is not something we can officially support. |
In particular, node_exporter 0.14.0 was built with go1.8.1 while 0.15.0 uses go1.9.1. |
Thanks a lot for feedback!
…On Oct 6, 2017 20:26, "Tobias Schmidt" ***@***.***> wrote:
In particular, node_exporter 0.14.0 was built with go1.8.1 while 0.15.0
uses go1.9.1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#691 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEbFsl7moGLwpzcicxis28dmTqw7X3OEks5spmKJgaJpZM4Pwx5M>
.
|
Host operating system: output of
uname -a
Linux vlnx300 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of
node_exporter --version
0.15 amd64
node_exporter command line flags
none
Are you running node_exporter in Docker?
no
What did you do that produced an error?
run node-exporter with no flags on RHEL5.5 x86_64
What did you expect to see?
node-exporter output like it was on 0.14
What did you see instead?
FATAL: kernel too old
Segmentation fault
The text was updated successfully, but these errors were encountered: