From the migrations in your log, you are coming from something in between v0.14.53 and v1.4.0, right? Version 10 is v1.6.0. Looks like some change since then broke the migration to 10. Given debian stable is on v1.0.1 and thus will have to go through this transition as well, I am interested in fixing this. Could you please create a copy of the index-v0.14.0.db directory in your syncthing config folder for testing before taking any further steps. To get your synchronisation up and running again, I suggest downloading v1.6.0 from github, and run that until the migration is done. Then upgrade to the latest version.
I am having a look at the code to see if the cause becomes clear like that. If not I’d very much appreciate if you could do some tests on the copied database (or privately make the db available for testing).
Actually this suggests a previous db migration failed at a later step and now it is retrying to do an earlier migration that already happened and fails due to that. Could you please check your Syncthing logs for migration errors before the one you posted here.
Here is index-v0.14.0.db you requested https://hdd.tomsk.ru/file/tczenmkf
Sorry for using our local file transfer service; much to my surprise I’ve discovered that I know nothing of more common file sharing services.
I’ve cloned 1.6.0 and I’m about to run the migration tomorrow if you have no test to perform on my database, it can wait a couple of days.
Sorry but I can’t locate the logfile.
/etc/conf.d/syncthing is like this:
# /etc/conf.d/syncthing: config file for /etc/init.d/syncthing
# User and group as which to run
# Configuration directory
# Log file location
# umask used to create files
# The default allows group access
# I/O nice level of syncthing
# Nice level of syncthing
# Extra options for syncthing
I have nothing in /var/log/syncthing except for empty file keep_net-p2p_syncthing-0