Joplin keeps showing "Syncing"

rxliuli · 2024-10-06T04:49:48.070Z

Operating system

macOS

Joplin version

3.0.15

Desktop version info

Joplin 3.0.15 (prod, darwin)

Client ID: 58f713f3db09496389ddc04056cf9930
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: 598677b

Backup: 1.4.2
Joplin Batch: 0.2.2
Joplin Publisher: 1.1.4

Sync target

OneDrive

Editor

Markdown Editor

What issue do you have?

In the case of a long startup, Joplin gets stuck in a synchronization deadlock. I suspect it's because I'm continuously calling the GET /folders? interface, but I'm not sure why there is a problem with this interface.

Screenshots

Snipaste_2024-10-06_12-41-28.png1230×1670 469 KB

image1228×2036 253 KB

Log file

last_1000_lines.txt (62.6 KB)

michal.borek · 2024-10-06T09:25:24.269Z

When I have problems like these I just delete the locks from the cloud drive (ensuring nothing is syncing at a time).

rxliuli · 2024-10-06T10:52:27.309Z

I can quit and reopen Joplin, which can temporarily solve this problem. But it's just annoying.

rxliuli · 2024-10-06T14:07:24.218Z

This problem has occurred again.

image1228×1070 167 KB

personalizedrefriger · 2024-10-06T19:42:35.686Z

I compiled instructions for how to get a stack trace for the "Synchronization is already in progress" message. However, I no longer think that a stack trace for this message will be useful — it seems to be coming from the regularly scheduled sync. I'm posting them here anyway because they might still be helpful for related debugging:

Debugging: Getting a stack trace

To get stack trace information for the "Synchronization is already in progress" error:

Open the "Sources" tab in Joplin's developer tools.
Press ctrl-p (I think cmd-p on MacOS).
Type Synchronizer.js and press enter.
Press cmd-f and search for Synchronisation is already in progress
Add a breakpoint to the line by clicking on the line number.
Wait for the breakpoint to be triggered.
Scroll to and inspect the "Call stack" section in the right sidebar.
Check the "Show ignore-listed frames" checkbox.

Screen recording demonstration

Note that it might be necessary to check "Show ignore-listed frames".

More useful might be determining where the synchronizer is getting stuck. Temporarily enabling debug logging might also help with this.

rxliuli · 2024-10-07T02:22:58.077Z

personalizedrefriger:

Synchronisation is already in progress

Thank you, I have recorded the Devtools Debugger video, and the logs have been enabled. If this issue occurs again, I will add it below.

personalizedrefriger · 2024-10-07T04:06:27.689Z

Thank you for the information! Based on the stack trace, the error message seems to be coming from the regularly scheduled sync:

github.com

laurent22/joplin/blob/d1ac3d415ea7665271accd581807e1e5ae56feef/packages/lib/registry.ts#L245


      
          			} else {
          				this.logger().debug(`Setting up recurrent sync with interval ${Setting.value('sync.interval')}`);
          
          				if (Setting.value('env') === 'dev') {
          					this.logger().info('Recurrent sync operation DISABLED!!!');
          					return;
          				}
          
          				this.recurrentSyncId_ = shim.setInterval(() => {
          					this.logger().info('Running background sync on timer...');
          					void this.scheduleSync(0, null, true);
          				}, 1000 * Setting.value('sync.interval'));
          			}
          		} finally {
          			this.setupRecurrentCalls_.pop();
          		}
          	}
          
          	// eslint-disable-next-line @typescript-eslint/no-explicit-any -- Old code before rule was applied
          	public setDb = (v: any) => {
          		this.db_ = v;

Unfortunately, this doesn't show where the ongoing sync is getting stuck. One possibility is fetchWithRetry in shim.ts), which retries a request after an increasing delay. However, for retryable requests, fetchWithRetry should fail after fetchMaxRetry_ = 5 failed requests (45000 ms + time for fetch to complete or fail).

rxliuli · 2024-10-09T03:14:42.920Z

The problem has occurred again, but I have enabled the debug log according to the instructions above.

image1770×858 200 KB

last_2000_lines.txt (128.8 KB)

personalizedrefriger · 2024-10-09T03:27:40.179Z

Thank you! I'm highlighting the last error before the repeated Synchronisation is already in progress. State: in_progresss:

Code: ENOTFOUND
FetchError: request to https://graph.microsoft.com/v1.0/drive/root:/%E5%BA%94%E7%94%A8/Joplin/locks/1_1_58f713f3db09496389ddc04056cf9930.json failed, reason: getaddrinfo ENOTFOUND graph.microsoft.com
    at ClientRequest.<anonymous> (/Applications/Joplin.app/Contents/Resources/app.asar/node_modules/@joplin/lib/node_modules/node-fetch/lib/index.js:1491:11)
    at ClientRequest.emit (node:events:514:28)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:514:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

One possible explanation: Joplin might not be setting Synchronizer.state_ back to idle. In particular, the call to releaseLock isn't wrapped in one of the try/catch blocks in Synchronizer.start_. As such, if an error occurs in releaseLock, Synchronizer.start might exit before setting state_ back to idle.

rxliuli · 2024-10-09T13:24:26.598Z

Okay, do I need to provide any other information? If necessary, I can also run the Joplin development environment locally, although I am not familiar with the internal code of the Joplin project

personalizedrefriger · 2024-10-09T17:36:08.903Z

rxliuli:

Okay, do I need to provide any other information?

If the issue was caused by the releaseLock issue mentioned above, it should be fixed by this pull request. Until a fix is merged/included in a release, be aware that disabling sync locks (available in the 3.1.x pre-releases) may also resolve the issue.

I don't think any other information is necessary.

rxliuli · 2024-11-08T17:04:40.952Z

Thank you, the issue has been confirmed to be fixed after updating to the latest version.