Syncthing panics and restarts cycle

I am a newcomer in the subject. I have a RPI4 with Openmediavault 4 and Syncthing v1.3.0 that is behaving very unstable with cyclical restarts. I want to use the NAS as a holder of replicas of directories from Win10 PCs. PCs with windows10 and Syntrayzor work perfectly between them replicating directories, no problem until now. The problem is when I set a win10 “Send” directory and configure it to replicate to a OMV directory. It behaves very unstable with service going down on the OMV end. I did set the STTRACE option and got a panic message as a report (several reports) which look to be something internal to Syncthing on OMV. On the windows10 side is reported: “WXIWO] 23:00:59 INFO: Connection to P5E5225 at closed: reading length: read tcp> wsarecv: An existing connection was forcibly closed by the remote host.” On OMV is reported the panic file with: "[P5E52] 22:15:15 INFO: Device WXIWOFG-UMG6B3M-HWIDMVY-FXBSDFP-6F6PXIM-ZM24N7A-K47KIFU-KD6T2QY client is “syncthing v1.3.0” named “LAD” Panic at 2019-10-13T22:15:48+01:00 panic: runtime error: slice bounds out of range

goroutine 89 [running]: panic(0x61b438, 0x10e0c038) /usr/lib/go-1.7/src/runtime/panic.go:500 +0x33c "

Can you help. Thanks. CTx

Full panic trace please?


panic-20191013-221548.log (48.3 KB)

syncthing v0.14.18-dfsg1 ... debian@debian 2017-04-29

You need to upgrade to something recent, that’s all.

I am confused. OMV reports to have version 3.11.1 installed: dpkg -l | grep openm ii libopenmpt0:armhf 0.2.7386~beta20.3-3+deb9u3 armhf module music library based on OpenMPT – shared library ii openmediavault 4.1.26-1 all openmediavault - The open network attached storage solution ii openmediavault-backup 4.0.6 all backup plugin for OpenMediaVault. ii openmediavault-cups 3.1.2 all OpenMediaVault CUPS (network printer server) plugin. ii openmediavault-diskstats 4.0.2-1 all OpenMediaVault disk monitoring plugin ii openmediavault-dnsmasq 3.1.5 all OpenMediaVault dnsmasq (local DNS and DHCP server) plugin ii openmediavault-flashmemory 4.2.1 all folder2ram plugin for OpenMediaVault ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ii openmediavault-locate 3.4 all locate plugin for OpenMediaVault. ii openmediavault-minidlna 3.3.11 all OpenMediaVault miniDLNA (DLNA server) plugin ii openmediavault-omvextrasorg 4.1.16 all Package Repositories for OpenMediaVault ii openmediavault-remotedesktop 4.0.1 all Remote desktop plugin for OpenMediaVault. ii openmediavault-remotemount 4.0.7 all Remote mount plugin for OpenMediaVault. ii openmediavault-resetperms 3.3 all Reset Permissions ii openmediavault-shellinabox 3.4 all Web-based SSH client. ii openmediavault-syncthing 3.11.1 all Syncthing plugin for OpenMediaVault.

And in fact this corresponds to the latest version for OMV4 Stable.

Can you clarify? Thanks. CTx

This is a pretty old version, so wherever you are getting it from, only has an old version.

OMV 4 is apparently based on Debian 9 (“stretch”) which includes Syncthing 0.14.18 which is two and a half years old and has the bug you ran into. Sorry.

As for why OMV calls the package version “3.11.1”… :man_shrugging:

As an update and clarification to this subject:

OMV package versioning 3.11.1 is in fact only related to the plugin package Openmediavault-Syncthing. Inside this Plugin I could have installed one of several Syncthing versions selectable by policy. I was “unlucky” to have the oldest installed automatically. As directed by OMV support, I managed to install manually the latest (1.3.0) Syncthing version (and keeping OMV-Syncthing plugin version unchanged !!!)

And Syncthing is now working as expected (bug is over) and much appreciated.

Thanks for your help. Cheers CTx


Would mind sharing, how you installed the latest version manually?

Just execute:

sudo apt-get install syncthing=1.3.0

It finds previous version and upgrades it.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.