-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
SNMP input: error in unmarshalResponse #9917
Comments
We don't have a way to reproduce this error because we don't have your snmp device, but I can share a few ideas about what might be related. It's possible that building with a new go version could cause this change but I think it's very unlikely. I would expect a compiler problem to affect more than just snmp walk. In the error log line, everything after I understand from the issue description that Telegraf 1.14.5 and 1.19.3 both work and 1.20.0 doesn't work. Telegraf uses the same version of the gosnmp library in 1.19.3 and 1.20.0, so we can rule out a change in the gosnmp module:
I noticed that in your tests you used two different telegraf.conf files. The first is telegraf 1.14.5 with Could you repeat your test with versions 1.20.0 and 1.19.3 but using the same config file. Please also post the config you use so we know for sure what telegraf is being asked to do. |
Config was the same, I was trying to remove some company specific info for more simple example, but missed second case, sorry. But if we still want to investigate a problem. Seems I was wrong about 19.3 being ok with that, maybe a miss during multiple versions changing. I've return all params as it was before and checked all major versions starting from 1.14.5 to 1.20, this case was broken somewhere between 1.18 and 1.19. Nothing was done between checks beside installing new version.
And 1.19
Is there any additional info I can provide? |
@reimda gosnmp v1.33.0 has some fixed regarding parsing lengths.. |
I updated gosnmp to 1.33.0 in #10076. When the CI build completes for that PR, could you test that change and see whether the error that started happening in telegraf 1.20 still happens? Thanks! |
The build is here: #10076 (comment). Click the dropdown triangle and choose your platform. |
Resolved by #10076 and included in telegraf 1.20, pleas reopen/comment if this did not solve the current issue. |
Hello @Hipska, @reimda
Config:
Testing on 1.18:
Testing on 21.4:
|
Okay, will reopen, please report this back faster next time. The issue you linked is this exact same issue. So did you try to link another issue? Please let us know which one so we can have a look as well.. |
Thanks a lot. It was mentioned here: |
Hi Team, |
On the server I have application with snmp interface support. Snmpwalk example:
And the following conf file:
At least on version 1.14.5 - everything works as expected:
But on version 1.20 and the same config we've faced an error:
I've checked on 1.19.3 and it works there as well. So I can only take a guess that it has something to do with new GO version implemented in 1.20
The text was updated successfully, but these errors were encountered: