Summary: | EWS gets stuck in "Retrieving collection tree" | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Aaron Williams <aaronw> |
Component: | EWS Resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | krissn, Martin |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Aaron Williams
2019-02-06 04:48:47 UTC
I stopped Akonadi and started it from the Alonadi console. The job tracker says Akonadi::CollectionFetchJob failed at CollectionRemoteId INBOX. The resource scheduler shows it waiting on SyncTags. When Akonadi gets stuck I see akonadiserver stuck at 100% CPU basically forever. I don't know if this is related to bug# 403903 but no matter what I did I was unable to synchronize my inbox folder which has a significant number of emails. My settings were identical to another machine. I was finally able to get it work by shutting down akonadi and kontact then replicating everything from the other computer including the database. Once I did that it started working again since it no longer had to download a lot of emails. Also, I saw it getting stuck in other stages besides retrieving collection tree. When the server tells the client it is busy the server may report that it will be busy for several minutes. I wonder if honoring the busy delay might help. When it stops, all EWS log activity stops. Thank you Aaron, for all your valuable bug reports. I am looking forward to use Akonadi EWS myself, however I am currently still stuck with KDEPIM 18.08.1 within Debian, at least until an updated Flatpak becomes available or I install KDE Neon or so into a VM. |