Hello, support.
I’m a long term user of Syncthing on my local Synology 216j NAS. In Feb I updated it to v2 without any issues.
A couple of days ago I saw usual update button on the top (I don’t remember the version though, I think it was 2.0.15) and clicked on it. It’s strange, because the latest build in SynoCommunity is 2.0.13-33.
Next morning syncthing stopped working on my nas completely. It just doesn’t start at all. When I click “Run” in Package Center it creates Syncthing icon on the synology OS desktop and in a couple of seconds it kills it and stops the app (it looks like a crash or sth like that).
Clean reinstall didn’t help. I even tried to find some leftover files via SSH and cleaned those as well.
I’m not sure if this will help but here is the content of syncthing.log file
There’s an incompatibility between the Synology kernel and the Go version Syncthing is currently built with. The Go project are working on a workaround for a point release.
Glad I checked here. I thought it was just me. The only clue I had from the log file was “futexwakeup addr=0x1850d30 returned -22
SIGSEGV: segmentation violation”.
I found a solution in another topic but I can’t call it simple. When you install syncthing it has “autoupdate” option turned on already, and it immediately updates to the latest (broken) version and that’s it, you can’t run it anymore.
So right after installation (dont run syncthing yet) you have to change config.xml file and disable that autoupdate option. I had to connect to nas via SSH, download that file and upload a changed one.
If somebody knows an easier way to disable autoupdate (maybe via some synology scheduler command?) then please post this info here.
I have confirmed this approach works. Unchecked the box for run after install. I have SSH enabled on my NAS so I used a terminal and vi to edit /var/packages/Syncthing/target/var/config.xml. Changed AutoUpgradeInterval from 12 to 0.
Hi. Could you please clarify one thing? How users will understand when the issue is fixed and it’s safe to update? Next syncthing update? Post in this topic?
In the meantime, it is technically possible to built syncthing with an older go version, or downgrade to an older version. The current SynoCommunity package ships with a version that works (v2.0.14-34), but it seems that this release has auto-upgrades enabled and therefore automatically upgrades to v2.0.15 on startup, which uses the latest version of the go runtime and hence fails. You probably need to disable auto-upgrades before starting syncthing, as mentioned in this post.
Dear all, may someone can help. I’v tried to disable Autoupdate according to this post but it seems on my Synology the path to the config file is a different one.
Some hints where I find the right config.xml would be great.
Dear all, I also has no /var/packages/Syncthing/target/var/config.xml file on my DS218j (DSM 7.1.1-42962 Update 9)
Righ now on my device Syncthing 2.0.14-34 installed, but not started. On start attemps I see Syncthing icons on desktop for 3-5s and after service
I think I’m in the same position with fsdgGFfgdf
It should be there. But in order to fix it you have to uninstall it first. Then install without auto-run after installation and only then you go and fix config.xml.
Dear devs, do we have any news regarding a real fix?
The package checks on upgrade what version of the binary is already present. If that one is newer than what the package ships (because of a prior auto-upgrade) then it leaves it untouched instead of overwriting with an older version.
If you re-enable upgrades and set upgradeToPreReleases to true, you should get 2.1.0-rc.2, which should work. In fact, it’d be nice if someone verified that.
