-
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
Internet Speed Monitor Input Plugin - fetching server list failed: unable to retrieve server list #9852
Comments
Just to update - problem still occurring in v |
What do you have the agent interval set to? The default of 10s? Because you are still successfully collecting other metrics and based on the error message you received, I do not think this is a bug in Telegraf. The error message This could mean you cannot get to the service. From the system where you are seeing errors can you see the following page: |
Global Agent - yes, 10s. This particular plugin - no, changed locally to 30m (as per code above).
I can connect without any issues from the Telegraf container - |
In the same place as you are running telegraf, can you try running the speedtest-go binary itself? Again, the error message is coming from the library, not telegraf, so something is not working on that side. |
I am going to try running your config locally overnight and see if mine starts erroring like yours. I did try using the speedtest-go binary for 30mins, running it every minute and only saw one issue during an upload with a broken pipe. |
I ran the this config overnight. I did get a handful of failures to get the server list, but hundreds of successful speed tests. The common thing I see across the errors is the date/time. Every error occurs exactly at the top or bottom of the hour. Is your test attempting to run then? Do your logs show something similar? |
My logs show exactly the same, I haven't had a single successful run, but all of the failures do seem to happen at :00 (the interval is set to 60 minutes). That still seems like a bug to me (not sure if telegraf or the speedtest-go though). |
I took the upstream speedtest-go binary and had it set to run as a cron at the top and bottom of the hour:
It also returned the same issue:
I am going to go ahead and close this as it is not specific to Telegraf, however, I would suggest opening a bug with the speedtest-go project and see what they say as well. Thanks! |
Thank you very much for your testing and effort @powersj |
You could still run every 60m or 30m but add some |
Relevant telegraf.conf:
System info:
System: Raspberry Pi 4 Model B Rev 1.4 8GB
OS/Kernel: Ubuntu 21.04 (Linux 5.11.0-1019-raspi) arm64 arch
Version: TELEGRAF_VERSION 1.20.0 from hub.docker.com tag
telegraf:1.20.0
Docker
Docker CE 20.10.8
Separate Overlay network for InfluxDB 2.0.8 and Telegraf 1.20.0.
All other plugins and Telegraf container able to communicate with the internet.
Steps to reproduce:
telegraf.conf
as per code abovetelegraf
container.Expected behavior:
Internet Speed measured by plugin and stored in InfluxDB database.
Actual behavior:
Telegraf container log:
The same error is produced on every interval attempt.
Additional info:
When I've used the plugin without
interval
parameter (so defaulting to agent's 10s) or with shorter duration (5m) during initial experiments, it was working fine for about half an hour. Then it suddenly stopped working without any other configuration changes. Other plugins are still working fine collecting other local system, local network and internet based metrics. Restarting telegraf container, InfluxDB container or the whole system doesn't improve the situation, which now lasts for about 24 hours.The text was updated successfully, but these errors were encountered: