I got the exact messages as others to update my current version of the app on my Mac. The app has been upgrading for about 20+ minutes now. I don’t think it’s the size of the total notes I have as I have very little.
From Joplin 1.0.239 to
Joplin 1.0.241 to
Joplin 1.0.242 (prod, darwin)
I only have Joplin on my Mac and the Dropbox app is on my Ipad. It was syncing perfectly before updating to v.1.0241. Is it possible that Dropbox is not on my Mac so it can’t find a target? There are no error messages either so I should wait longer?
What happens exactly, what screen do you see?
Same problem here, the only screen I'm seeing is the
Joplin upgrade in progress...
Please wait while the sync target is being upgraded. It may take a few seconds or a few minutes depending on the upgrade. The application will automatically restart once it is completed.
screen...
That's all, no further error messages. Left it running several hours each time. That was on Arch Linux latest build.
But same on windows.
Also tried command-line joplin on Arch with
/!\ Sync target must be upgraded! Run sync --upgrade to proceed.
sync --upgrade
Synchronization target: Nextcloud (5)
15:12:31 MigrationHandler: Sync target version is 0 or 1 - creating "locks" directory: [object Object]
15:12:31 MigrationHandler: Acquiring exclusive lock
and stopping there...
btw, had 239 (at least I think so), first tried 241 than 242 any finally 245, all the same behavior...
@lordasgart, is it still doing this with the CLI app? Normally acquiring an exclusive lock has a timeout of 30 seconds so it shouldn’t get stuck like this.
Also is there something special about your network connection? Like custom SSL certificates, proxy, etc?
Yes, it’s still doing this. I can see getting the lock acquired, because the corresponding lock file is refreshed via the Nextcloud desktop sync after several seconds again and again.
I’m using a valid Let’s Encrypt SSL certificate on my own server, no proxy or something else. Also tried from my office computer via normal internet connection and via LAN, but there is no difference.
One thing perhaps: I’m using a own user “joplin” on my Nextcloud for synchronization. So I didn’t create a sub-folder “Joplin” and suggested and so I’m using the following sample URL for synchronization: https://example.com/remote.php/dav/files/joplin
instead of the currently suggested URL
https://example.com/nextcloud/remote.php/webdav/Joplin
So far this has worked without problems.
I just tried to use my standard user for my Nextcloud and created a folder Joplin and wanted to do an initial sync with that, and this is what I got:
Synchronization target: Nextcloud (5)
Starting synchronization...
Completed: 14/09/2020 09:20 Last error: Error: MKCOL locks/: Parent node does not exist (Exception Sabre\DAV\Exception\Conflict) (409): <?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="sabre/dav">
<s:exception>Sabre\DAV\Exception\Conflict</s:exception>
<s:message>Parent node does not exist</s:message>
</d:error>
/!\ Sync target must be upgraded! Run sync --upgrade to proceed.
sync --upgrade
Synchronization target: Nextcloud (5)
09:20:19 MigrationHandler: Sync target version is 0 or 1 - creating "locks" directory: [object Object]
MKCOL locks/: Parent node does not exist (Exception Sabre\DAV\Exception\Conflict) (409): <?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="sabre/dav">
<s:exception>Sabre\DAV\Exception\Conflict</s:exception>
<s:message>Parent node does not exist</s:message>
</d:error>
I’ve released a new CLI version, which should fix issues with clock sync issues between local device and server. Could you give it another try and see if it helps?
New version should be 1.0.168
Hi,
I just downloaded https://github.com/laurent22/joplin/archive/v1.1.1.tar.gz (1.0.168 version) from https://github.com/laurent22/joplin/releases
and build and started it with
npm install
cd CliClient
npm start
and the upgrade was successful!
After that I could use my installed Electron version 1.0.245 too again.
After the first start he still asked for an upgrade, but I killed it, and after deleting the exclusive lock, everything seemed to work normally with the Electron version 1.0.245 too…
Thanks for your help…
Here same problem with:
Joplin 1.0.339
Android 10,
Samsung note 9
Joplin 1.0.339
Synced using webdav
Probably after upgrading to Android 10
I get a banner with the following writing:
the sync target needs to be upgraded. Press this banner to proceed
But after hours nothing happens even if I have only less than 100 notes.
So what should I do?
Thanks Laurent,
"errors only" shows nothing.
It does not allow me to select parts of the logs to post here, but the most relevant part seems the following:
"Sync version of the target (1) is lower than the version supported by the client (2). Please update the sync target"
then it reports always:
"preparing scheduled sync
Search engine: updated FTS table in 208 ms. Inserted 1. Deleted 0."
then it finishes with
" Got lat/long"
Thinking about it:
I imagine the client (2) is the android cell phone and the target (1) is what?
The android cell phone is synced with a webdav server and the same webdav server is synced with my debian computer.
So which is the target (1)? Is it the webdav server or is it the debian computer?
Debian computer Joplin is version 1.0.193, which is certainly lower than android Joplin version 1.0.339.
So should I understand that the problem is updating debian Joplin?
So I upgraded debian joplinAppimage to 1.0.241 which should be the last one. This worked, debian Joplin made the same sync target upgrade, rebooting and seems working and syncing as before, but Android did not improve, it is always stopped on the same banner requesting a sync target upgrade that never ends.
But now Android log has some errors:
Cannot acquire sync lock: either the lock could be written but not read back, Or it was expired before it was read again,
then it gives many index numbers such as
index.android.bundle:1336:5802
But now, clicking on the banner resolves the issue. So finally the problem was that the Joplin appimage on the computer was too old