Sync failure -> info.json limit?

Support
1

Bug report #7866 filed on this... While I'm waiting for a response from @laurent, has anyone else experienced this problem?

I have Joplin configured to sync from my primary machine to a RPi 4 running ownCloud and nginx. After years of reliable operation, sync stopped working sometime on February 27th with the following error message:

Last error:  FetchError: response timeout at https://192.168.1.4/owncloud/remote.php/webdav/Joplin-SYNC/info.json over limit: 120000

I get this error with both Nextcloud sync (used for years) and Webdav sync options. Clearly it's a timeout issue, but not sure what info.json does. Any ideas?

All iOS clients also fail to sync so it's gotta be on the server side...

2

Not sure why, but I´ve been unable to sync in a similar matter. I also use webdav. The error that appears seems to be related to JSON files

Last error: Error: DELETE locks/2_1_f939c3ddb2dc46a38ef90ffa32d4aa59.json: Unknown error 2 (400): �ad

I´ve checked the login cred and all is good. Since my server at Bluehost went down a few days ago it did not come back to normal

3

I looked at info.json in my Joplin sync folder and it's....empty. But the date the file was last modified was 27 February, the same date when sync stopped working. Hhhmmm....

4

OK, on the theory that "if it's broke, it can't get any more broke" I intrepidly deleted info.json from the sync folder on the target device (RPi4 as above). I attempted a complete "upload of local data to sync target" refresh via WebDav under the Advanced Settings page, which resulted in the following:

Error
The sync target could not be upgraded due to an error. For support, please copy the complete content of this page and paste it in the forum: https://discourse.joplinapp.org/

The full error was:

Could not upgrade from version 1 to version 2: PUT info.json: "Joplin-SYNC/info.json" is locked (Exception OCA\DAV\Connector\Sabre\Exception\FileLocked) (423): <?xml version="1.0" encoding="utf-8"?> <d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns"> <s:exception>OCA\DAV\Connector\Sabre\Exception\FileLocked</s:exception> <s:message>"Joplin-SYNC/info.json" is locked</s:message> </d:error>

Error: Could not upgrade from version 1 to version 2: PUT info.json: "Joplin-SYNC/info.json" is locked (Exception OCA\DAV\Connector\Sabre\Exception\FileLocked) (423): <?xml version="1.0" encoding="utf-8"?> <d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns"> <s:exception>OCA\DAV\Connector\Sabre\Exception\FileLocked</s:exception> <s:message>"Joplin-SYNC/info.json" is locked</s:message> </d:error>

at newError (/tmp/.mount_Joplin5OWcau/resources/app.asar/node_modules/@joplin/lib/WebDavApi.js:414:11) at WebDavApi.exec (/tmp/.mount_Joplin5OWcau/resources/app.asar/node_modules/@joplin/lib/WebDavApi.js:441:11) at process.processTicksAndRejections (node:internal/process/task_queues:96:5) at async FileApiDriverWebDav.put (/tmp/.mount_Joplin5OWcau/resources/app.asar/node_modules/@joplin/lib/file-api-driver-webdav.js:201:10)

5

This is a problem with ownCloud, unlock the file in ownCloud. Check the ownCloud forum for help to this topic. When you search here you would find myn pepole withe the same problem and ownCloud.

6

How do I unlock the file?

7

FIXED! In the spirit of brute-force solutions, I created a new sync folder on ownCloud and pointed all of the clients to it.

8

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