-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
nixos/open-webui: try to fix the database readonly issue #431395
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Attribute statedir
is missing. You probably meant to write stateDir
.
This seems to have fixed the readonly db issue. I already lost my webui.db before while upgrading as mentioned in the addressed issue already. I'm now able to setup everything again at least! Thanks a lot 😄 |
Cool, I'll rebase this properly when I'm back at my office. |
Co-authored-by: Tim <[email protected]>
bc3d049
to
af749a3
Compare
I have not yet deleted my database. |
@MayNiklas You can try setting the changes from here manually in your own config (before updating to 0.6.18) like this: services.open-webui = {
enable = true;
...
environment = {
STATIC_DIR = "${config.services.open-webui.stateDir}/static";
DATA_DIR = "${config.services.open-webui.stateDir}/data";
HF_HOME = "${config.services.open-webui.stateDir}/hf_home";
SENTENCE_TRANSFORMERS_HOME = "${config.services.open-webui.stateDir}/transformers_home";
};
}; then moving your data ( sudo cp /var/lib/open-webui/webui.db /var/lib/open-webui/data
sudo cp -r /var/lib/open-webui/cache /var/lib/open-webui/data
sudo cp -r /var/lib/open-webui/uploads /var/lib/open-webui/data
sudo cp -r /var/lib/open-webui/vector_db /var/lib/open-webui/data and finally, try to update to the 0.6.18 version of open-webui.
I've just confirmed with @pinage404 that this method works without data loss! |
I still don't understand why moving stuff from one directory into a subdirectory would make things magically work. Can you explain? |
I unfortunately also have no idea why this change suddenly seems to work. When testing this PR, I noticed, new data (databases, etc.) would be saved and written under #430433 (comment) mentions, that it was just to match upstream defaults. Happy to test anything if wanted. 👍 |
Then we have no garantee that the issue won't show up again? |
It's really a mystery to me as well. |
I wish I could understand why this issue is happening right now, never had the issue before.
Anyway, this should fix #430433 but there might be data losses.
Things done
passthru.tests
.nixpkgs-review
on this PR. See nixpkgs-review usage../result/bin/
.Add a 👍 reaction to pull requests you find important.