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

Speedtest not working when mounting a volume #64

Closed pro4tlzz closed 3 years ago

pro4tlzz commented 3 years ago

Hi all,

I am using Docker Run to start the container with the code

docker run -d \ --name=speedtest \ -p 7123:80 \ -v /home/myuser/Containers/Config/speedtest/results:/var/www/html/data/ \ roest/docker-speedtest-analyser

I am on Ubuntu 20.04.

Whenever I try to do a speedtest from the it does not log the result to a file or show the result on the web Ui. If I run the container without persistent storage it works fine.

The browser console says Failed to load resource: the server responded with a status of 404 (Not Found) & Failed to load resource: the server responded with a status of 404 (Not Found)

I know the volume is mounted correctly as if I create result.csv in the directory I can see the results.csv when I bash into the container. If I also bash into the container I am able to create the result.csv

The container logs just show 2020-12-25T17:27:58.608597551Z --- running speedtest --- 2020-12-25T17:32:28.631339859Z --- running speedtest --- 2020-12-25T17:33:18.912350739Z --- running speedtest ---

and lots of this 2020-12-25T17:27:25.056834316Z 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) 2020-12-25T17:27:25.058034978Z 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: 2020-12-25T17:27:25.058042767Z no field package.preload['resty.core'] 2020-12-25T17:27:25.058044841Z no file './resty/core.lua' 2020-12-25T17:27:25.058046407Z no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua' 2020-12-25T17:27:25.058047914Z no file '/usr/local/share/lua/5.1/resty/core.lua' 2020-12-25T17:27:25.058049396Z no file '/usr/local/share/lua/5.1/resty/core/init.lua' 2020-12-25T17:27:25.058050857Z no file '/usr/share/lua/5.1/resty/core.lua' 2020-12-25T17:27:25.058052295Z no file '/usr/share/lua/5.1/resty/core/init.lua' 2020-12-25T17:27:25.058053892Z no file '/usr/share/lua/common/resty/core.lua' 2020-12-25T17:27:25.058055396Z no file '/usr/share/lua/common/resty/core/init.lua' 2020-12-25T17:27:25.058056919Z no file './resty/core.so' 2020-12-25T17:27:25.058058397Z no file '/usr/local/lib/lua/5.1/resty/core.so' 2020-12-25T17:27:25.058059827Z no file '/usr/lib/lua/5.1/resty/core.so' 2020-12-25T17:27:25.058061244Z no file '/usr/local/lib/lua/5.1/loadall.so' 2020-12-25T17:27:25.058062695Z no file './resty.so' 2020-12-25T17:27:25.058064086Z no file '/usr/local/lib/lua/5.1/resty.so' 2020-12-25T17:27:25.058065663Z no file '/usr/lib/lua/5.1/resty.so' 2020-12-25T17:27:25.058067213Z no file '/usr/local/lib/lua/5.1/loadall.so')

gpoul commented 3 years ago

Had the same issue; the problem for me was that nginx is running as user nginx with uid 100, but uid 100 wasn't allowed to write on the mounted volume's file; a workaround for me was to create a file with the right permissions on the mounted directory. (you can use the result.csv contained in the git repo as a sample content that will work)

pro4tlzz commented 3 years ago

Had the same issue; the problem for me was that nginx is running as user nginx with uid 100, but uid 100 wasn't allowed to write on the mounted volume's file; a workaround for me was to create a file with the right permissions on the mounted directory. (you can use the result.csv contained in the git repo as a sample content that will work)

Yup I somehow managed to get it working, think this was the issue. All good now though