-
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 not working since upgrading to 1.21.4 #10810
Comments
Same symptoms, same problem here, using debian stretch. |
Hi @Serverlag and @elacour, we recently merged a change that switches back to the 1.20.4 behavior (#10802). It's in the nightly build now. Could you try the nightly build to see if it works for you? We're planning to release this in 1.23.0 which is scheduled for next Wednesday, March 23. If you could report what you find it would help us flush out bugs and gain confidence in the change. Nightly builds: https://github.com/influxdata/telegraf/blob/master/docs/NIGHTLIES.md |
Hi @reimda, so far promising results. Looking at below logs during start we see no further SNMP errors, SNMP data collection is working and I can confirm data in influxdb for all existing inputs I was using in both 1.19 and 1.21. If I notice any further issues I will report them as requested.
|
Good to hear. Thanks for testing, @Serverlag! |
just tested, it works, thanks! |
Relevant telegraf.conf
Logs from Telegraf
Restarting Telegraf
System info
telegraf 1.21.4
Docker
No response
Steps to reproduce
Expected behavior
1.21.x releases should work with existing mibs that were working in 1.19.1 and 1.20.4
Actual behavior
Errors generated during service restart, errors generated in telegraf log and also no data in influxdb for expected snmp inputs.
Additional Info
Downgrading to 1.20.4 resolves the issue, I have found both #10793 and #10445 which seem to indicate they are also experiencing SNMP issues post 1.21.x upgrade.
The text was updated successfully, but these errors were encountered: