-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
corrupt entry appears cause database locked issue / prevent ALL sync of that calendar #291
Comments
m10d
changed the title
fail to parse cal entry *may* cause database locked issue
fail to parse cal entry appears cause database locked issue / prevent ALL sync of that calendar
Mar 23, 2023
m10d
changed the title
fail to parse cal entry appears cause database locked issue / prevent ALL sync of that calendar
corrupt entry appears cause database locked issue / prevent ALL sync of that calendar
Mar 23, 2023
Emphasize that while I don't know if Android app noticed this failure, it did sync the offending cal entry (I was able to search for it by the person's name from the desktop(linux) logs, edit it, save it, and succesfully sync all that) I'd expect the behavior here to:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tl;dr is that one of my calendars refused to sync anything to Thunderbird; after cleaning up a single offending, somehow apparently** corrupt cal entry, everything syncs fine.
**
during this time, android apps synced fine, and I do remember seeing a sync warning somewhere (in thepim...
web app perhaps?), I never had any problems syncing my data between android phones.steps / background, for completeness:
long time etesync user on several android's; new user of etesync-dav
set up easily w/
systemd
, 5 calendars. 4 synced quickly & seemingly completely in thunderbird.The fifth calendar was displaying an
!
, and in the non-debug logs I have adatabase locked
failure. zero entries from this calendar displayed in thunderbird.attempt force fix the 'locked' issue via
.dump
command:sync in TB,
!
persists, same withdatabase locked
enable
-D
and restart servicefind a
failure-to-parse
stacktrace error immediately afterdatabase locked
line. No other errors.CN=
field - this happened to be a contact with only a handful of calendar events containing their infosynced android, restart
etesync-dav
, resync TBissue resolved, full missing calendar syncs
The text was updated successfully, but these errors were encountered: