Hi all,
for me its even working with v2.0.16 on a Synology 923+ with DSM 7.3.2-86009 Update 3.
Syncthing v2.0.16
Package v2.0.14-34
br
A couple of days of use shown that both rc2 and 2.1 Release actually doesn’t work well on my Synology. I mean it’s not crashing as before, it starts and works a bit, but after couple of minutes strange things happen.
All remote devices disconnect, I am offline for them as well, synology resource monitor shows CPU and HDD loading from syncthing process but visually nothing happens in Syncthing. ST doesn’t respond to restart/shutdown commands. I tried to reinstall it completely but nothing helped until I installed v2.0.14-34.
Does anyone have similar problems?
Anything in the logs?
In the syncthing.log there are only connect/disconnect reports but there is another file panic-20260511-144921.reported.log that has thousands of suspicious strings.
This exact file has been saved right before I decided to replace rc2 to Release but it was already “broken” in a way I described above. I couldn’t update ST by usual upgrade button so I uninstalled rc2 and installed Release manually. Then it didn’t work, so I tried clean installation (uninstalled it with all the data) and now I don’t have any newer logs from Release version because I use v2.0.14-34.
If this log is not useless then I could spend some more time to install Release to get similar log file if it will help to fix the problem.
Here is the log file without IDs and IPs
panic-20260511-144921.reported.log (310.3 KB)
Hi there,
I have just updated my Syncthing from release 2.0.14-34 to 2.0.16-35 and it won’t start on my DS414 (7.1 armadaxp). Is there any way to roll back the version without losing all my settings? Can I help you understand what is not working by sharing logs? I don’t know where to get them, so I need directions for this
Same problem here with 2.0.16-35 on a DS214play.
The package has auto-upgraded itself and syncthing seems to stop immediately after being started manually. If there are any details or logs you’d like to see to help debug/fix just let me know!
Same problem here with 2.0.16-35 on a DS218j.
Instant crash, and I dont understand what to do, is the reinstall + disable updates trick mandatory ?
I just tested this last night on my DS218j. Upgraded from v1.30 to 2.0.16 via the SPK package, then let the internal updater jump to 2.1.1 fully automatically. The migration went very smooth and now it’s working fine on the current version.
We definitely need logs to find the cause for termination.
Hello, I oberve the same issue and on my Synology 214 Play with DSM 7.1.1-42962 Update 9. Syncthing does not start and crashes instantly with SIGSEGV: segmentation violation
According the package manager I am on 2.0.16-35 and this is the latest version available.
Can someone advise how to proceed? In /volume1/@appdataappdata/synthing I currently now have config.xml, config.xml.new and config.xml.v37. config.xml.new is the newest and the date fits the update date, but is significantly smaller.
-rw------- 1 sc-syncthing synocommunity 36940 Apr 14 20:47 config.xml -rw------- 1 sc-syncthing synocommunity 2729 May 10 18:23 config.xml.new -rw------- 1 sc-syncthing synocommunity 38002 Apr 14 20:47 config.xml.v37
Edit: diff showed configuration version 51 in config.xml, while version 35 in config.xml.new and version 37 in config.xml.v37. I assume config.xml is the right one to keep and discard the older ones. I found the upgradeToPreRelease setting in config.xml as well,
How can I update to the latest version as syncthing instantly crashes?
Regards
syncthing.log (4.4 KB)
From what I understand, upgrading from a version in the 1.x to 2.1.x is now safe through SPK 2.0.16-35 (because of fast-forward to fixed version), but for people like me and @x1r5 stuck with spk 2.0.16-35 trying to launch a crashing <2.1.x internal version what is the recommended path for fixing ?
- SSH and delete some binary for redownload ?
- Pre-reinstall first ? Cleanup “internal data” too ?
Thanks
I was able to proceed and solved my issues (for now). I uninstalled syncthing and kept the data, ssh-ed into the system and renamed the syncthing directory, re-installed syncthing and started the application.
This went fine and in a second step I stopped syncthing, copied my backup/config.xml to syncthing/config.xml and started the application again. Currently it’s scanning the directories and hopefully will start syncing soon.