0.11.19 SQLite Db Errors #701
Comments
|
Same issue here, I moved from latest tag back to |
|
I've ended up moving back as well to .17 and its working. |
are you using .env file? docker-compose? can you provide more info please? thanks. in my case, .19 wasn't reading .env correctly, I moved all env variables to docker-compose file, and now everything's working fine. But I use MariaDB, not sqlite. |
|
|
Same issue here, I moved from latest tag back to image: 'ghcr.io/alexjustesen/speedtest-tracker:v0.11.17', as well. speedtest-tracker-vpn:
container_name: speedtest-tracker-vpn
image: 'ghcr.io/alexjustesen/speedtest-tracker:v0.11.17'
restart: unless-stopped
security_opt:
- no-new-privileges:true
network_mode: "service:gluetun"
depends_on:
gluetun:
condition: service_healthy
#ports:
# - '8090:80'
# - '8443:443'
environment:
- 'PUID=${SPEED_PUID}'
- 'PGID=${PGID}'
- 'TZ=${TZ}'
- 'UMASK=${UMASK}'
volumes:
#- '/etc/localtime:/etc/localtime:ro'
- '${DOCKERAPPDATA}/config/speedtest-vpn:/config'
- '${DOCKERAPPDATA}/config/speedtest-vpn/appdata:/etc/ssl/web'
healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220
test: "curl -sf https://example.com || exit 1"
interval: 1m
timeout: 10s
retries: 1
labels:
- "deunhealth.restart.on.unhealthy=true"
- "com.centurylinklabs.watchtower.enable=true"
#- "com.centurylinklabs.watchtower.monitor-only=true"```
```2023-08-31 00:44:14
✅ App key exists
2023-08-31 00:44:14
2023-08-31 00:44:14
🔐 Linking the storage...
2023-08-31 00:44:14
[2023-08-31 04:44:14] production.ERROR: Database file at path [/var/www/html/database/database.sqlite] does not exist. Ensure this is an absolute path to the database. (Connection: sqlite, SQL: PRAGMA foreign_keys = ON;) {"exception":"[object] (Illuminate\\Database\\QueryException(code: 0): Database file at path [/var/www/html/database/database.sqlite] does not exist. Ensure this is an absolute path to the database. (Connection: sqlite, SQL: PRAGMA foreign_keys = ON;) at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php:801)
2023-08-31 00:44:14
[stacktrace]
2023-08-31 00:44:14
#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(755): Illuminate\\Database\\Connection->runQueryCallback()``` |
|
same issue here, watchtower automatic update and I back to v0.11.17 and this is work |
|
Looks like v0.11.18 removed sqlite support
Seems this statement wasn't completely true.
Originally posted by @alexjustesen in #669 (comment) |
|
Same Issue. Use Sqlite. Back to 0.11.17 |
|
Hi how can I set the watchtower not updated speedtest tracking? It is possible? Because my set is 04:00am run all docker compose file updated. |
Set a label on the container - com.centurylinklabs.watchtower.enable With a value of false |
Radarr - https://hotio.dev/containers/radarr/radarr: Sonarr - https://hotio.dev/containers/sonarr/sonarr: lidarr -https://hotio.dev/containers/lidarr/lidarr: qBittorrent - https://docs.linuxserver.io/images/docker-qbittorrentqbittorrent: Watchtower (automatic docker container updater) - https://github.com/containrrr/watchtowerwatchtower: Jackett - https://hotio.dev/containers/jackett/jackett: Bazarr - https://hotio.dev/containers/bazarr/bazarr: onzu/homebride - https://docs.docker.com/compose/install/homebridge: speedtest-track: |
|
Same issue, went back to 0.11.17, which corrected the issue |
|
same error. Back to 0.11.17 to solve the error. |
|
Same here. I will wait for Alex before going back :) |
|
same issue. I solved it to swtich from sqlite file to mysql database. |
|
Since last upgrade I can't login, don't see errors using Sql too |
|
It's also failing the MariaDB version, also went back to 0.11.17. |
|
Same...back to 0.11.17 and all good. |
|
Oops... |
sqlite still not functioning on |
|
I get the same error messages but the speedtest-tracker does work normally |
|
You'll need to pass an I'll update the docs later today with how to use sqlite as a DB just know going forward its intended for backwards compatibility only and the recommended DBs will be MySQL/MariaDB and Postresql. Once #676 is done I'll be working on #591 so you can migrate from SQLite to any of the other options. |
|
My apologies if this is somewhere mixed into this huge gnarly thread, but is 0.11.21 working on unRAID? Default install, no existing appdata, and I'm getting the following. In Connection.php line 801: SQLSTATE[HY000] [2002] Connection refused (Connection: mysql, SQL: select * In Connector.php line 65: SQLSTATE[HY000] [2002] Connection refused This is a clean install on a new server, had this on a previous server a while back and wanted to start using it again. I came across this thread and have seen numerous comments about unRAID and it not working. |
|
@StirCwazy this is what works for me on Unraid. Note that I setup a separate db for speed test:
To get the APP_KEY value, run the following command for your speedtest-tracker container: |
|
UNRAID: I had it on v0.11.17. I changed the template back to "latest". Forced an update and it failed to start. Same errors. Stopped and restarted and it works. I guess the Unraid APP template is going to need to be revised to include mariadb/mysql or postsql databases. |
Am I understanding then that a sqlite DB is no longer an option? |
I added back the symlink in |
It is still kind of bugged, as it requires two runs to start successfully. |
I don't own the template but I'll post in the forums for an update. |
Caching I think has something to do with it |
|
I forgot to mention, ZappyZap's Unraid template doesn't use enviroment variables except for |
|
Maybe not by default but you can add them |
|
@alexjustesen If using unraid, are there any other variables I'd need to use if opting for sqlite? |
|
@StirCwazy I'm actually using Unraid for this myself, however I'm using the @alexjustesen sorry I just meant it creates a |
No worries, I'm marching towards getting rid of the the
What @SaltireSoul is correct, you just need those two vars. |
|
Adding these to Unraid: Resulted in: Removed them. Started and it failed. Restarted and it worked. |
Added both variables, got the same 500 | Server Error. Removed as you said you tried with success, failed. In Connection.php line 801: SQLSTATE[HY000] [2002] Connection refused (Connection: mysql, SQL: select * In Connector.php line 65: SQLSTATE[HY000] [2002] Connection refused |
|
@StirCwazy config looks right, not sure if it was the unraid forums or here but it required a second restart for the container to pickup the env variables. |
Okay, I tried it again and it worked. UPDATE @alexjustesen : I added the following variables to Unraid and set up a MariaDB (Linuxserver image) container: I had to do the same start, stop, and restart to clear the 500 error code. Seems to be working. |
|
I will update the template with this |
That's really weird , but yes it is the case. |
After adding the variables for DB_CONNECTION and DB_DATABASE it worked after a restart. I've been busy and haven't had a chance to reply, so my apologies to all. |
|
#746 merged to dynamically generate an |
|
Seems it's not creating the db if it doesn't exist. How to start using this image when no preexisting sqlite db exists? Should be documented I believe |
|
Using SQLite added to the FAQ |
I try this method but not work for me. I back to v0.11.17 |
|
I moved to MariaDB. |
If you're still having problems please open a new issue and we'll get it sorted. I'll be unsubscribing from this one |
and others
Seeing db errors with the latest release. Since I used Watchtower - it pulled down the latest 0.11.19 and now the container wont come back up. Have multiple deployments effected.
Assuming this is related to the SQLite changes? How does one fix this? Was a working deployment - only update was the container.
The text was updated successfully, but these errors were encountered: