macOS: stuck on sync for two days

Support
1
  • The version you are using:
Joplin 2.8.8 (prod, darwin)
Client ID: 74107cfe910f454cb38599fcf0765eb1
Sync Version: 3
Profile Version: 41
Keychain Supported: Yes
Revision: c2a6a13
  • If it is a sync issue, please let us know what you are syncing with:
    Dropbox
  • The operating system you are using:
    macOS Monterey 12.6.1

One of my Macs has been stuck on attempting to sync for two days. I have other Macs, Android devices, and iPhones that sync to the same Dropbox target which are working fine.

Attempting to cancel the sync has no effect - except to display Cancelling... indefinitely.

Safe mode has no effect. Rebooting, etc., no effect.

The only errors I'm seeing in log.txt are a couple sync errors from about a week ago, such as:

Synchronizer: "Error: Cannot acquire sync lock because the following client has an exclusive lock on the sync target: (1 #d2c3e6b09a744b9098fd456d56fc285b)
Code: hasExclusiveLock
Error: Cannot acquire sync lock because the following client has an exclusive lock on the sync target: (1 #d2c3e6b09a744b9098fd456d56fc285b)
    at LockHandler.<anonymous> (/Applications/Joplin.app/Contents/Resources/app.asar/node_modules/@joplin/lib/services/synchronizer/LockHandler.js:202:31)
    at Generator.next (<anonymous>)
    at fulfilled (/Applications/Joplin.app/Contents/Resources/app.asar/node_modules/@joplin/lib/services/synchronizer/LockHandler.js:5:58)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)"

However I'm not seeing any errors from the past two days, except on loading plugins when I entered safe mode.

In the console (debug mode) I'm seeing a bunch of warnings about updating components like:

Please update the following components: Connect(MainScreenComponent), Connect(MenuBar), Connect(NavigatorComponent), Connect(RootComponent), Provider
/Applications/Joplin…evelopment.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

... which I'm assuming aren't affecting the sync issue.
And two plugin related warnings:

DevTools failed to load source map: Could not parse content for file:///Users/xxx/.config/joplin-desktop/cache/Bishoy.EmailPlugin/ui/style/bootstrap.min.css.map: Unexpected end of JSON input

DevTools failed to load source map: Could not parse content for file:///Applications/Joplin.app/Contents/Resources/app.asar/gui/note-viewer/pluginAssets/mermaid/mermaid.min.js.map: Unexpected end of JSON input

However, entering safe mode and disabling plugins has no effect on the sync issue.

2

I've been researching how to deal with this sync issue, as the app is content to spin and attempt to sync indefinitely, hours/days at a time, without any warnings, errors, or guidance to the user. I never found anything definitive in the console or logs.

After 5 full days of Joplin not able to complete a sync on one computer, fired it up today and it completed a sync right away. No intervention from me whatsoever - I've been researching but never took any action.

Is there a S.O.P. for dealing with "stuck" sync issues like this? I couldn't find anything definitive in Help/Support, in these forums, on Reddit, etc.

Not being able to sync work notes for 5 days killed my productivity. There's got to be a way to deal with sync issues right? I really don't want to migrate away from Joplin but I can't be down for 5 days again with no idea what to do.

Update: I have not yet updated to today's release, still on 2.8.8

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.