Speedtest suddenly stopt working (only manual test works)

[Mosdn85]

Hi all,

For almost a week dockers speed test analyser stopped working.
Manual testing is working.
I've uninstalled & re-installed it, but its the same problem

I got the following errors, when i checked the logs.

--- running speedtest ---
Traceback (most recent call last):
File "/var/www/html/scripts/speedtestRunner.py", line 62, in
runSpeedtest()
File "/var/www/html/scripts/speedtestRunner.py", line 27, in runSpeedtest
s.get_best_server()
File "/usr/lib/python2.7/site-packages/speedtest.py", line 1491, in get_best_server
raise SpeedtestBestServerFailure('Unable to connect to servers to '
speedtest.SpeedtestBestServerFailure: Unable to connect to servers to test latency.

Any ideas what the problem is?

WKr,
Mo

[GitBeto21]

Hi,
I have same issues here; since 8th March
😩

[hccp-slogemann]

Same for me, stopped working since 8th of March

[KossikCZ]

Yeah, mine too. Since March 8th as well. :( I am puzzled to see why, as running the test manually via web or cli works. :/

[Chris122AT]

Same problem here!

[contisegler]

I had the same problem. Setting the environment variable CRONJOB_ITERATION solved the problem for me. I only tested this with a 5 minute interval though.

[GitBeto21]

I have setup this variable since the installation, because I used a shortener itineration then 60min. and still it does not work. i have just changed the time, and now works again.
What about this alert:
[alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised
And this error:
[error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/
??? 🧐

[contisegler]

For the five minute interval all speed tests work except at the full and half hour. I can only speculate why this is the case. Maybe running speedtest.py in debug mode at the full or half hour might give more information.

[GitBeto21]

it makes sense. because I choose 30 min, and it was empty, now I choose 10, and I see results for 10, 20, 40, 50

[Mosdn85]

I had the same problem. Setting the environment variable CRONJOB_ITERATION solved the problem for me. I only tested this with a 5 minute interval though.

Hi,
How did you do that?
Like this?

[Mosdn85]

Fixed also with me when i added environment variable "CRONJOB_ITERATION" with value 5
With value 30, same problem

[arubacao]

Can confirm.

• start manual speedtest is working
• CRONJOB_ITERATION != 60,30 is working (so something like 29,59)
• CRONJOB_ITERATION == 60,30 is NOT working

[Mosdn85]

Can confirm.

• start manual speedtest is working
• CRONJOB_ITERATION != 60,30 is working
• CRONJOB_ITERATION == 60,30 is NOT working

Hi arubacao,

You only add "!" next to CRONJOB_ITERATION and it works?

[arubacao]

@Mosdn85 Ah no, I mean something that is simply not 30 or 60. I just use 57 instead of 60 and this works for me.

[stevietv]

looks like the error is coming from sivel/speedtest-cli (https://github.com/sivel/speedtest-cli/blob/c58ad3367bf27f4b4a4d5b1bca29ebd574731c5d/speedtest.py#L1490-L1491)

the packaged speedtest is not able to return the best server at

docker-speedtest-analyser/scripts/speedtestRunner.py

Line 27 in 52b5773

s.get_best_server()

[Bagestu]

Okay, so it appears that I'm not the only one. Too bad I only tried changing 60 to 30... Thanks a lot for figuring out that we can get this working again by putting any value except 60 or 30 for the cronjob.

For now I'll change the cron through bash so I can make it run every 60 minutes again, but with an offset, as it otherwise still fails at the 30th and 60th minute intervals. Removing the "*/" from the existing cron should do the trick:
*/15 * * * * (every 15 minutes) then becomes 15 * * * * (15 minutes past every hour).

This might be a good thing to add for a future release, @roest01. Because if a docker is restarted, it'll reset the cronjob value.