Speedtest-for-InfluxDB-and-Grafana icon indicating copy to clipboard operation
Speedtest-for-InfluxDB-and-Grafana copied to clipboard

Published 20 hours ago • verified publisher icon barrycarey

Ping 30 minutes

Open bmorris591 opened this issue 6 years ago • 1 comments

Looks like the ping is recorded at 30 minutes when the speed test fails, the time (30 minutes) is the same as the interval between tests which makes me suspect a bug in the ping changes.

2019-02-01 17:10:46,027 - INFO: Waiting 1800 seconds until next test
2019-02-01 17:40:46,127 - INFO: Starting Speed Test For Server None
2019-02-01 17:40:48,170 - INFO: Selected Server 15815 in London
2019-02-01 17:40:48,171 - INFO: Starting download test
2019-02-01 17:40:48,303 - INFO: Starting upload test
2019-02-01 17:40:50,691 - INFO: Download: 0.0Mbps - Upload: 0.0Mbps - Latency: 1800000.0ms
2019-02-01 17:40:50,692 - INFO: Waiting 1800 seconds until next test

bmorris591 avatar Feb 03 '19 10:02 bmorris591

That's really odd. Off the top of my head I can't think of why that would happen. The ping is set on the speedtest-cli side each time it sets the server. This happens before before each run of this script.

When I have some time I'll dig into it and see if I can find anything on my side that would cause it.

barrycarey avatar Feb 03 '19 12:02 barrycarey