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
Error in plugin: performing bulk walk for field myfield-program: Request timeout (after 3 retries) #8271
Comments
From the errors it looks like the snmp agent is not responding. You may want to make sure you can get the table using the snmptable command from net-snmp to confirm that the snmp agent is responding before trying to get it with telegraf. It might also help to try again with telegraf but without docker to rule out docker as the problem. |
Thank you for reply @reimda snmptable and snmpwalk or snmpbulkwalk are working fine but it seems to be the only thing with the telegraf. |
Having the same problem. Running telegraf in a docker container causes: |
So more information: I can open bash inside the telegraf container and run Running telegraf on the machine directly also works just fine. Also I tried adding the agent to the telegraf container network and using docker's inter-container networking and everything started working perfectly. Edit: Running the agent on a separate machine also works fine. Also using https://github.com/qoomon/docker-host as a middle-man also works just fine. |
I had this exact issue on Centos 7.9 outside of docker. I adjusted timeouts, intervals, connection jitter etc, and tested against a few agents all with similar results. I then tested my same configuration, but with SNMP v2 and have had zero failures. |
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Page. Thank you! |
Every SNMP command like snmpwalk, snmptable and snmpbulkwalk are working but telegraf commands are being timeout.
Relevant telegraf.conf:
System info:
Telegraf 1.15.3
Docker
Steps to reproduce:
Expected behavior:
It should collect data and inset in influxdb
Actual behavior:
Additional info:
The text was updated successfully, but these errors were encountered: