Closed Jaxel closed 9 months ago
having same issue ,using sqlite in Unraid docker lasted version
I have t he same issue on Portainer - Docker
running: ghcr.io/alexjustesen/speedtest-tracker:latest
Gets the following error:
In Connection.php line 829:
SQLSTATE[HY000] [2002] Connection refused (Connection: mysql, SQL: delete f
rom cache
)
In Connector.php line 65:
SQLSTATE[HY000] [2002] Connection refused
same error here since this morning.
The issue is caused by #1084.
To revert back to the old default behaviour, set the environment variable CACHE_DRIVER
to file
.
@alexjustesen Breaking changes like this should probably be moved to major version upgrades or at least have better logging so the users know what is causing the issue and can fix this without needing to look at the commit history.
Until the error is fixed you can go back to last working version, by changing image line to:
image: 'ghcr.io/alexjustesen/speedtest-tracker:v0.14.4'
The issue is caused by #1084. To revert back to the old default behaviour, set the environment variable
CACHE_DRIVER
tofile
.@alexjustesen Breaking changes like this should probably be moved to major version upgrades or at least have better logging so the users know what is causing the issue and can fix this without needing to look at the commit history.
Doing this return a new error about missing encryption keys. Don't know what that is.
@Jaxel tried:
It still broken
Confirmed adding this to my yml in my environment variables section fixed it:
- CACHE_DRIVER="file"
Confirmed, adding CACHE_DRIVER as a new variable in the UnRaid template fixes it and it now works.
Following. Will you report here when a new verison is released that solves the issue? Will the new environment variable be needed in future versions?
when there is breaking changes like this being done on a version, can you kindly add them to a changelog/release notes for that version so people would know how to fix vs just having it break and having to stumble across a github issue
The issue is caused by #1084. To revert back to the old default behaviour, set the environment variable
CACHE_DRIVER
tofile
.
Sadly this doesnt work for me. Still the exact same error.
I am attempting to install speedtest-tracker with a new Postgres database. First, using 0.14.4 fixed the issue. But my log is different from what has been pointed out by existing users, so I thought that I would add it FWIW:
2024-02-02T07:50:42.132509923-08:00 stdout F 🐇 Configuring Speedtest Tracker... 2024-02-02T07:50:42.132511472-08:00 stdout F 2024-02-02T07:50:42.132512796-08:00 stdout F 🔒 Fixing app path file permissions... 2024-02-02T07:50:42.141796543-08:00 stdout F ✅ Permissions fixed. 2024-02-02T07:50:42.14180724-08:00 stdout F 2024-02-02T07:50:42.141809294-08:00 stdout F 🧹 Clearing any previous caches... 2024-02-02T07:50:42.339491616-08:00 stderr F [2024-02-02 15:50:42] production.ERROR: SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "cache" does not exist 2024-02-02T07:50:42.339505037-08:00 stderr F LINE 1: delete from "cache" 2024-02-02T07:50:42.339506737-08:00 stderr F ^ (Connection: pgsql, SQL: delete from "cache") {"exception":"[object] (Illuminate\\Database\\QueryException(code: 42P01): SQLSTATE[42P01]: Undefined table: 7 ERROR: relation \"cache\" does not exist 2024-02-02T07:50:42.339508029-08:00 stderr F LINE 1: delete from \"cache\" 2024-02-02T07:50:42.339518148-08:00 stderr F ^ (Connection: pgsql, SQL: delete from \"cache\") at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php:829) 2024-02-02T07:50:42.339519517-08:00 stderr F [stacktrace]
I won't bore you with the stacktrace.
For those having cache issues, follow the debug steps in this comment: https://github.com/alexjustesen/speedtest-tracker/issues/1035#issuecomment-1924907035
For those having cache issues, follow the debug steps in this comment: #1035 (comment)
have: CACHE_DRIVER=database
in .env file
@alexjustesen Since upgrading speedtest-tracker to v0.14.5 I have the same issue as the topic starter. I did not changed anything before upgrading (from v0.14.4). I just created a new container with the new v10.14.5 image. I had no environment variable CACHE_DRIVER in my .env file (nor in my docker compose file) so speedtest-tracker used the default value 'file'.
Setting the environment CACHE_DRIVER to database does not solve the issue. I have now reverted back to image v0.14.4; speedtest-tracker is working again.
Here's my Portainer YAML file - The CACHE_DRIVER setting didn't solve it for me either, so I also stay on 0.14.4
services: speedtest-tracker: container_name: speedtest-tracker ports:
APP_KEY="xxxxxx"
volumes:
image: 'ghcr.io/alexjustesen/speedtest-tracker:v0.14.4'
restart: unless-stopped
Setting CACHE_DRIVER=file
only worked for me after I manually removed the container and then did a docker compose up -d
again. Now I'm at latest
and speedtest-tracker is working again. It doesn't work if you don't remove the old container.
Setting
CACHE_DRIVER=file
only worked for me after I manually removed the container and then did adocker compose up -d
again. Now I'm atlatest
and speedtest-tracker is working again. It doesn't work if you don't remove the old container.
I did remove the old container/image and redownloaded it, all through Portainer. Didn't work for me.
Setting the environment CACHE_DRIVER to database does not solve the issue. I have now reverted back to image v0.14.4; speedtest-tracker is working again.
Did you restart the container after changing the config?
@alexjustesen, sure I did. After that I checked in the container with "php artisan about" if "cache" indeed was set to database; it was.
CACHE_DRIVER worked for me, ONLY after I completely deleted the /config/www
folder.
The solution for me was to change DB_HOST env variable to DB_DATABASE. After that, no need to manually specify CACHE_DRIVER.
Will not boot since this morning. On Synology Container Manager.