Speedtest-Tracker
Speedtest-Tracker copied to clipboard
[BUG] - No MaxMind license key found; exiting. Please enter your license key into /etc/conf.d/libmaxminddb
Describe the bug First off I love Speedtest-Tracker, it had been running fine untouched (with 232 successful hourly tests completed) but then after one failure (invalid date) and then a subsequent successful run, it just stopped. Checking the logs it referred to the error “ No MaxMind license key found; exiting. Please enter your license key into /etc/conf.d/libmaxminddb ”. Container was still up, that hadn’t stopped.
To Reproduce
- Nothing I can suggest, as it had worked fine 232 previously..
Expected behavior
- I didn’t expect it to silently stop running..
Screenshots
- Screenshot to show the log entry
Context
- OS: Docker
- Speedtest-Tracker Version: 1.12.0
Additional context Nothing I can think of, I did restart the container, and everything is running again, I’ve just lost a couple of days of test results.
Same problem here. Nothing touched, last success test was 15.04.2022
@nodecentral It's not a problem with license key... Check a permission to your volume, chmod 777 solved problem
Hi @Dropsik - QQ: if it is a permissions issue, why would it have worked 200+ times before?
Same here, although I'm late to get on the train as I have found out only today...
Same problem here - nothing touched. Speedtest suddenly stopped tracking a week ago
Same here. Happens suddenly
Happened to me too..running for a year, no getting that message
Same issue here every couple of days. After I restart the container everything returns to normal.
To make things even more "fun" the key that breaks the entire program isn't exposed as a docker variable/env key nor is it visible in the overlay FS. So you have to ssh into the container and add it that way, this is very clearly a bug.
To make things even more "fun" the key that breaks the entire program isn't exposed as a docker variable/env key nor is it visible in the overlay FS. So you have to ssh into the container and add it that way, this is very clearly a bug.
Hi, I moved to a fork of this : https://github.com/alexjustesen/speedtest-tracker/ It's well maintained for now and seems to work better.