-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Metricbeats panics in kvm dommemstat metricset #7792
Labels
Comments
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Jul 31, 2018
Improper error handling caused a panic when connection to libvirtd couldn't be stablished. Cleaned up error handling a little bit. Fixes elastic#7792
jsoriano
pushed a commit
that referenced
this issue
Jul 31, 2018
Improper error handling caused a panic when connection to libvirtd couldn't be stablished. Cleaned up error handling a little bit. Fixes #7792 The default settings for the kvm module didn't work. Updated to connect to the unix socket by default, and provide a hint on how to setup access to libvirtd running on remote hosts.
jsoriano
pushed a commit
to jsoriano/beats
that referenced
this issue
Oct 23, 2018
Improper error handling caused a panic when connection to libvirtd couldn't be stablished. Cleaned up error handling a little bit. Fixes elastic#7792 The default settings for the kvm module didn't work. Updated to connect to the unix socket by default, and provide a hint on how to setup access to libvirtd running on remote hosts. (cherry picked from commit 76d3949)
jsoriano
pushed a commit
to jsoriano/beats
that referenced
this issue
Oct 23, 2018
Improper error handling caused a panic when connection to libvirtd couldn't be stablished. Cleaned up error handling a little bit. Fixes elastic#7792 The default settings for the kvm module didn't work. Updated to connect to the unix socket by default, and provide a hint on how to setup access to libvirtd running on remote hosts. (cherry picked from commit 76d3949)
jsoriano
added a commit
that referenced
this issue
Oct 24, 2018
Improper error handling caused a panic when connection to libvirtd couldn't be stablished. Cleaned up error handling a little bit. Fixes #7792 The default settings for the kvm module didn't work. Updated to connect to the unix socket by default, and provide a hint on how to setup access to libvirtd running on remote hosts. Co-authored-by: Adrian Serrano <adrisr83@gmail.com> (cherry picked from commit 76d3949)
jsoriano
added a commit
that referenced
this issue
Oct 24, 2018
Improper error handling caused a panic when connection to libvirtd couldn't be stablished. Cleaned up error handling a little bit. Fixes #7792 The default settings for the kvm module didn't work. Updated to connect to the unix socket by default, and provide a hint on how to setup access to libvirtd running on remote hosts. Co-authored-by: Adrian Serrano <adrisr83@gmail.com> (cherry picked from commit 76d3949)
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
Improper error handling caused a panic when connection to libvirtd couldn't be stablished. Cleaned up error handling a little bit. Fixes elastic#7792 The default settings for the kvm module didn't work. Updated to connect to the unix socket by default, and provide a hint on how to setup access to libvirtd running on remote hosts. Co-authored-by: Adrian Serrano <adrisr83@gmail.com> (cherry picked from commit 6de03f7)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For confirmed bugs, please report:
Enable kvm module:
Run metricbeat
Results:
Stacktrace:
The text was updated successfully, but these errors were encountered: