-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] QueryFailedError: SQLITE_ERROR: no such table: settings on fresh install #679
Comments
Hey, i’m not exactly sure what i’m looking at. Is this the full log? Before starting the ui & server process, there should be database migrations. These migrations create the table you’re missing. Does it say anything else before booting the server? Is it possible you’re not booting the container with the correct entrypoint script when using ansible? |
Hi. Yes, full log - or more precisely the part the repeats itself. I didn't see anything else. The log just continuously loops the same info. Shouldn't be a migration as there's nothing to migrate from, it's a brand new install. RE: entrypoint. Um, I don't see any defined entrypoint. I'm working off the docker compose file shown in the instructions.
With Ansible just becomes:
End result is I get a 0 byte maintainerr.sqlite file in persistent data directory. I chmod +777'd it for testing and no difference. Did I miss something in the instructions? Are the instructions missing something? |
There’s no instruction missing. It should perform all migrations before starting anything else. When there’s no database file present, the process should create the file and run all migrations. The migration log would be the very first thing logged. Perhaps something else went wrong ( folder permissions?) Could you try to run the container without Ansible (just with normal compose)? |
Sure.
result:
I also deleted the existing 0 byte maintainerr.sqlite file and the same looping errors continue. sudo chmod +777 * -R 'd the data dir and same results. tree
|
So for shits and giggles I ran
...and I have the exact same problem.
|
This is what a correct log should look like. The
|
The logs were so big that I just copied and pasted what I found to be looping from the tail and obviously missed some stuff for the head. Here is the complete log after removing everything, re-pulling, and running for 10 seconds:
|
Doesn't make sense to me as the app obviously works for you and others, but Googling "env: can't execute 'node': Text file busy" will show others with that error where it was resolved by downgrading to node 20.2 and earlier. EDIT: This issue might be of interest. If I read it right linuxserver.io rebased a bunch of their images related to this issue: nodejs/docker-node#1912 |
Well, this isn't a Maintainerr issue. It's a bug between Node.js 20+ and older Linux kernels. The solution is to update your kernel. You could try to add the 'UV_USE_IO_URING=0' environment variable to your docker compose. This should also mitigate the issue. I've added the flag by default in #725. |
fix(build): Added a workaround for the 'Text file busy' error when us…
Yeppers. That did the trick. |
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
App looks very useful, anxious to try it out!
Describe the bug
New install, SQL errors. Please see below pasted logs.
To Reproduce
Steps to reproduce the behavior:
Installed basically following instructions, using Ansible instead of Docker Compose. Diffs are memory restraint of 512mb and a bunch of traefik labels.
Expected behavior
webserver start and access app
Screenshots
n/a
Device (please complete the following information):
Additional context
LOGS:
The text was updated successfully, but these errors were encountered: