While updating syncthing to v13, my browser disconnected. As expected, the update failed and syncthing won't start at all. So I restored it from a previous snapshot, and now it runs fine. The problem is, freenas thinks it is v13 (its in the sqlite db), while the version running is actually v12 (can be seen in Actions/About menu).
Now, how do I actually update it? I really need to update it because every other device has updated already and none of them can communicate with syncthing on freenas anymore because v12 => v13 is not a backward-compatible update.
I can think of some ways:
1. Reinstall and reconfigure everything. This is the safest, and also the most time-consuming way. I don't really want to do so much work.
2. Install a new instance of syncthing and then copy over all the files from /var/db/syncthing inside the old jail t the new jail. This may (mostly) take care of configuring the new installation, but I'd still need to reconfigure all the other devices that sync to it.
3. Install a new instance of syncthing v13 (a new jail, like in syncthing_2), and copy over all the v13 files to my existing v12 jail. The best way to do it (that I can think of) is with "rsync -pog --delete --links" so that ownership and permissions are preserved, symlinks are created with identical targets and extraneous files are deleted. It worked when I restored v12 from the snapshot. But that had the same jail for source & destination. Copying files from some other jail would likely require a lot of diff'ing and trial & error.
4. Backup the config.db, change the version of syncthing in plugins_plugins table, and restore freenas from that db. This looks like the least work, and also the riskiest. I'm not sure what I could lose by restoring from config.db, even if it takes only a couple of minutes to change the db and restore it back. Or whether this would be enough to actually force freenas to update syncthing.
Any other ideas?
Regards,
Saurav.
Now, how do I actually update it? I really need to update it because every other device has updated already and none of them can communicate with syncthing on freenas anymore because v12 => v13 is not a backward-compatible update.
I can think of some ways:
1. Reinstall and reconfigure everything. This is the safest, and also the most time-consuming way. I don't really want to do so much work.
2. Install a new instance of syncthing and then copy over all the files from /var/db/syncthing inside the old jail t the new jail. This may (mostly) take care of configuring the new installation, but I'd still need to reconfigure all the other devices that sync to it.
3. Install a new instance of syncthing v13 (a new jail, like in syncthing_2), and copy over all the v13 files to my existing v12 jail. The best way to do it (that I can think of) is with "rsync -pog --delete --links" so that ownership and permissions are preserved, symlinks are created with identical targets and extraneous files are deleted. It worked when I restored v12 from the snapshot. But that had the same jail for source & destination. Copying files from some other jail would likely require a lot of diff'ing and trial & error.
4. Backup the config.db, change the version of syncthing in plugins_plugins table, and restore freenas from that db. This looks like the least work, and also the riskiest. I'm not sure what I could lose by restoring from config.db, even if it takes only a couple of minutes to change the db and restore it back. Or whether this would be enough to actually force freenas to update syncthing.
Any other ideas?
Regards,
Saurav.