Just registered to report that the package update above appears to have wiped the Syncthing config (other than the device ID) on my DS920+ running DSM7 and I have to recreate the shares etc. A word of caution to other users.
EDIT: Just to clarify, Syncthing’s internal update mechanism had updated the binary to version 1.19.0 without any issue but a subsequent package update published by SynoCommunity and available from within DSM’s package center caused the problem.
I had the same thing happen. If you want to preserve your existing client sync configurations/relationships, DO NOT TAKE THIS PACKAGE UPDATE.
You already have the Syncthing code updated via its own autoupdate mechanism.
I urge the SynoCommunity to pull back this package. There is no warning about the extensive damage it does and reconfiguration that will be required. Especially concerning for people with lots of different folders sync’d.
This is not the synocommunity - you should report to them asap. This topic might still helpful in reaching other Syncthing users on synology, but it is not the right place to report a bug and get it fixed, that would be here I guess: Issues · SynoCommunity/spksrc · GitHub
Historically, @acolomb has had some involvement with the SynoCommunity package. Highlighting for awareness, just in case. But, what Simon says – do report in the appropriate places as well.
Same here, after using the package center update, my config was gone. I took a while until synchting was up and running again. But i still have to reconfig all my settings.
@murchu, @dingo, @zendnez, @Jengo, @d3rm4tz3 would any of you happen to be confident enough to handle manual backup / restoring of the Syncthing config folder on the DS?
I could provide preview packages when we have a fix ready for testing. But would strongly advise to make a proper config backup first before trying a downgrade / upgrade again with the testing package. One important thing would be to stop the Syncthing service before making such a backup.
Sure, no problem. I haven’t reconfigured it yet but will do shortly, at least in part. Is it just the config.xml file in /@appdata/Syncthing needs to be backed up?
PS re ‘repair package’: for me that was required post-update to DSM 7 but did not result in any loss of data at that time.
Same happened to me. I thought I would uninstall and then re-install just to clear out everything 100%, but now the package has been removed so I’m stuck without a working setup.
with 1.19.0-24 only options.conf and config.xml were overwritten with the former default files contained in the spk file of the downloaded package.
A workaround would have been to delete the /var/packages/syncthing/target/var folder (NOT/var/packages/syncthing/var !!!) before the update, but as 1.19.0-24 is not available for download anymore, you have to wait for 1.19.0-25 anyway.
And thank you for picking up work on this so quickly. We have a fix imminent and I suppose a new version might be published today. Without your help, I definitely could not have handled this problem within one day of the initial report!
Syncthing v1.19.0-25 is now uploaded to the synocommunity package center (and available for manual download and installation) and will appear in the DSM package center of the diskstations within 48h.
