-
Notifications
You must be signed in to change notification settings - Fork 644
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
invalid memory address or nil pointer dereference Error #169
Comments
Can you run the exporter with |
@SuperQ was minimally faster, so my only remaining point: Please change your login credentials and take care to blank/remove everything, ideally making even the length of the strings invisible to anyone you send this to. |
@SuperQ and @RichiH thanks for your reply. |
I traced the error, it looks like it's coming from the upstream SNMP code. I will have to see if there are any related upstream issues filed/fixed. |
Thanks @SuperQ for your time. |
There's nothing specific upstream that I can find after a quick glance through the changes. However it looks like the v3 auth has been refactored since we released the last snmp_exporter. I propose we update the vendoring and test again. |
okay |
If possible, can you build a version of the snmp_exporter from master? |
Never done them before. |
If you have a Golang compiler/build env setup, it should be as easy as |
No i have not setup Golang |
Here is a |
Thanks @SuperQ Thanks again :) |
Great! We'll have to make a new official release that contains the updated vendor code. |
FYI, I've made an official release of the new version. |
Hi, the problem seems to be back: Using version 0.12.0 with docker image.
snmpwalk is working with the device, so the problem is not on the side of the device for sure. From log.level=debug returns:
|
Hi,
I am getting invalid memory address error when using snmp v3 authentication.
The exporter was working fine with snmpv2 devices with default_if_index module.
Below is the error, yml config , snmpbulwalk command output from the box.
The text was updated successfully, but these errors were encountered: