search

roest01 / docker-speedtest-analyser

Automated docker speedtest analyser tool with included web interface to monitor your internet speed connection over time. Setup at home on your NAS (Synology, QNAP tested) and the container runs hourly speedtests. The speedtest results are displayed in an webinterface as line graph(s) over the day.
Other
108 stars 47 forks source link

Docker Speedtest does not work anymore #55

Closed stele99 closed 3 years ago

stele99 commented 3 years ago

With the latest release the docker speedtest does not work. speedtest is not performed anymore. no automatic speedtests, no manual speedtest.

log when starting the image: Starting run.sh Starting Cronjob Starting nginx nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [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/en/download.html (rc: 2, reason: module 'resty.core' not found: no field package.preload['resty.core'] no file './resty/core.lua' no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/5.1/resty/core.lua' no file '/usr/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/common/resty/core.lua' no file '/usr/share/lua/common/resty/core/init.lua' no file './resty/core.so' no file '/usr/local/lib/lua/5.1/resty/core.so' no file '/usr/lib/lua/5.1/resty/core.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './resty.so' no file '/usr/local/lib/lua/5.1/resty.so' no file '/usr/lib/lua/5.1/resty.so' no file '/usr/local/lib/lua/5.1/loadall.so')

stevietv commented 3 years ago

having the same issue here. also getting the following log entry everytime the cronjob should run:

/bin/ash: /var/www/html/scripts/speedtestRunner.py: Permission denied

Bushwacker2020 commented 3 years ago

Echoing this issue. I pulled the image with the "develop" tag and it still works. Seem to be a lot of projects that are encountering issues with LauJIT.

JacobOkanta commented 3 years ago

Also having this issue was originally getting the /bin/ash: /var/www/html/scripts/speedtestRunner.py: Permission denied error. Tried removing and recreating the container and started getting the LuaJIT errors. While using the "develop" tag may work it should be noted that according to the Docker Hub that version was last updated 2 years ago.

tuckshoprn commented 3 years ago

I'm also having this issue.

Container log is:

Starting run.sh, Starting Cronjob, Starting nginx, nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html), nginx: [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/en/download.html (rc: 2, reason: module 'resty.core' not found:, no field package.preload['resty.core'], no file './resty/core.lua', no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua', no file '/usr/local/share/lua/5.1/resty/core.lua', no file '/usr/local/share/lua/5.1/resty/core/init.lua', no file '/usr/share/lua/5.1/resty/core.lua', no file '/usr/share/lua/5.1/resty/core/init.lua', no file '/usr/share/lua/common/resty/core.lua', no file '/usr/share/lua/common/resty/core/init.lua', no file './resty/core.so', no file '/usr/local/lib/lua/5.1/resty/core.so', no file '/usr/lib/lua/5.1/resty/core.so', no file '/usr/local/lib/lua/5.1/loadall.so', no file './resty.so', no file '/usr/local/lib/lua/5.1/resty.so', no file '/usr/lib/lua/5.1/resty.so', no file '/usr/local/lib/lua/5.1/loadall.so')

After this I attached to the container and manually added the OpenResty repository for alpine and installed it following the instructions https://openresty.org/en/linux-packages.html
I then got

/bin/ash: /var/www/html/scripts/speedtestRunner.py: Permission denied

appearing in the log

I checked the permissions on this file and it is not execute enabled. I ran chmod +x on it and now it works.

EDIT: It seems adding the OpenResty repository is not required, as even after I add and install, I still get the same log when starting nginx in the container. The Permission Denied message comes when a test is attempted.

I rebuilt the Dockerfile adding 'RUN chmod +x /var/www/html/scripts/speedtestRunner.py' at the end, and now it works. I still get the OpenResty messages when the container starts - regardless of whether I build it with or without "apk add openresty apk add openresty-resty"

fudge01010 commented 3 years ago

Been doing some testing, and coming to the same conclusion as @tuckshoprn - seems to be a permissions issue. Running the latest docker tag, and then doing chmod 755 speedtestRunner.py seems to partially fix it - I get speedtest results in the console when I click the 'start manual speedtest' button, with them being written to the .csv successfully.

Going to send a PR shortly :) but anyone else with the issue in the meantime, changing script to executable seems to fix it.

Note: If you had any speedtests done and saved to your csv between what looks like #53 and #54, then no new results will appear on your graph, even though they are being recorded.

You will either need to remove the bad results from your csv (the timestamp is 1000x smaller than the others, easy to spot), or create a new file.

stevietv commented 3 years ago

thanks for doing the PR @fudge01010 - lets wait for it to get merged. note: if you add "fixes #55" to the PR description it should link PR and issue and allow both to be closed

jaxjexjox commented 3 years ago

Ok I thought this was me and my results.csv was damaged or something.

Thanks guys.

jaxjexjox commented 3 years ago

Yeah the chmod change fixed stuff.

jaxjexjox commented 3 years ago

Did this get wrapped up? I'm curious if I can update yet.

stevietv commented 3 years ago

not yet, still waiting for @roest01 to merge PR #57

EVOTk commented 3 years ago

Hello, I have the same problems :(

Synology DS918+ / DSM 6.2.3

tuckshoprn commented 3 years ago

The latest release fixed this for me. You may need to reset the csv file if previous versions have entered incorrectly formatted data.

EVOTk commented 3 years ago

Thank you for the answer. It works now, but the error is still present on launch.