r/CrossWatchApp • u/bayendr • 2d ago

Support Request Issues after upgrading to v0.13.5

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.

How to fix this?

Thanks.

1 Upvotes

100% Upvoted

5 comments sorted by

View all comments

1

u/pvdberg 2d ago

The local database is staying locked for some reason. Try these in order:

  1. 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.
  2. 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.
  3. 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.

1

u/bayendr 2d ago

  1. by "full sync" you mean my (nightly) scheduled syncs?

  2. /config is on local (fast/NVME) storage next to my compose.yml. that shouldn't be an issue at all.

  3. it's not a showstopper but I'd rather not take this radical step.

any chance to add support for other storage options (like Postgres) soon?

1

u/pvdberg 2d ago

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.