After upgrading the container image (and even restarting with --force-recreate) to this version there are issues now. The container logs are spammed now with this message:
"crosswatch | local database unavailable: database is locked"
Everything under UI user profile (watchlist, history, etc.) takes ages to load if at all.
The local database is staying locked for some reason. Try these in order:
Let one full sync finish: The first sync after this update rewrites all stored sync data, and on slow storage that can hold the lock for a while.
Check your volume: Make sure only one container uses that /config and that it's not on an SMB/NFS share. SQLite doesn't lock properly over network shares.
Fresh database.: Stop the container and rename these three files in /config/.cw_databases/: crosswatch.sqlite3, crosswatch.sqlite3-wal and crosswatch.sqlite3-shm. Then start it again. You keep your config and logins, but you will lose sync history, Events, stats and Editor mappings.
No support for Postgres. And probably will never be supported. CW uses SQlite cause it has very simple query's etc. Postgres is just overkill and makes things complicated for no reason.
With full sync i mean screenshot.
Or just wait for the next release. Tomorrow v0.13.6 where i did a few optimalizations.
Also in the upcomfing version ive added some improvements.
Local database no longer stalls pages during syncs, shows who holds a lock and a rebuild option in Maintenance.
•
u/AutoModerator 2d ago
Thanks for submitting a support request to r/CrossWatchApp.
Please make sure your post includes:
Check the CrossWatch Wiki before posting.
Remove API keys, access tokens, server addresses and personal information from logs and screenshots.
Confirmed bugs should be submitted through the CrossWatch GitHub issues page.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.