I’ve been running syncthing for 6 mos or so with great results until now. My setup is a couple of servers (linux desktops - one with a static IP) and various laptops which are off and on line from time to time. I added a third linux server w/ static IP to sync a nightly backup file. Small test files in the folder sync fine as usual. However, the backup itself (1.9gb) makes it into the tmp status on the destination machines (.syncthing.filename.tar.tmp) and shows a size of 1.9gb but the sync never completes. Ideas?
Also, it shows up in the gui under “out of sync items”
Thanks
Thanks I’ll try that. Have to reset the log file since there are no timestamps on log entries. However some grepping reveals no "error"s or mentions of the big file.
In existing log files it seems that “…ID… closed: reading length: EOF” migth be a clue??
Thanks. Not sure what you mean by “cuts out”. The big file doesn’t make it to any destination machines, 24/7 desktops or laptops (which are indeed on and off from time to time). Here is a recent (de-identified) log excerpt from laptop side:
2019-09-19 06:47:39 Connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR closed: reading length: EOF
2019-09-19 06:47:41 Established secure connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 192.168.0.25:56334-104.193.226.100:22067 (relay-server) (TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305)
2019-09-19 06:47:41 Device ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR client is "syncthing v0.14.43-ds1" named "xxxxxxx4514"
2019-09-19 06:49:11 Connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR closed: reading length: EOF
2019-09-19 06:49:13 Established secure connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 192.168.0.25:56356-104.193.226.100:22067 (relay-server) (TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305)
2019-09-19 06:49:13 Device ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR client is "syncthing v0.14.43-ds1" named "xxxxxxx4514"
2019-09-19 06:50:43 Connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR closed: reading length: EOF
2019-09-19 06:50:45 Established secure connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 192.168.0.25:56374-104.193.226.100:22067 (relay-server) (TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305)
2019-09-19 06:50:45 Device ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR client is "syncthing v0.14.43-ds1" named "xxxxxxx4514"
2019-09-19 06:52:15 Connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR closed: reading length: EOF
2019-09-19 06:52:27 Established secure connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 192.168.0.25:56404-104.193.226.100:22067 (relay-server) (TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305)
2019-09-19 06:52:27 Device ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR client is "syncthing v0.14.43-ds1" named "xxxxxxx4514"
2019-09-19 06:53:57 Connection to ZB5HDBC-xxxxxxxx-xxxxxxxxxx-W6WYSNR-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR closed: reading length: EOF```
By “cuts out” he is referring to Connection to ZB5HDBC... closed: reading length: EOF which leads to the “Disconnected” state in the UI. Is beagle per-chance running a newer version of Syncthing? There’s an issue with with versions <0.14.46 when syncing with >1.2.0 (and 1.x with a non-default setup). If that’s the case, update blake, if not you need to troubleshoot the network. I’d start with checking logs on beagle, as the EOF (not timeout) suggests it’s the other side that drops the connection.
Thanks for reply!! Here are recent logs from beagle (yyy.yyy.yyy is beagle’s static IP). Versions may be the issue. Beagle is a very recent install. I’ll try to update others. However, small files sync just fine between the machines.
[UCHGH] INFO: Connection from UQ3G4FJ-WR7ME4I-ZG6JHPA-6OJLIS4-DJJIADH-YS4IB4D-P3DYOD4-GFUNMQH at 128.xxx.xxx.xxx:59248 (tcp-server) rejected: unknown device
[UCHGH] INFO: Connection to ZB5HDBC-EQOLHUS-*********-*********-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 128.yyy.yyy.yyy:33552-209.141.59.16:22067/relay-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_$$$$$$$$$_POLY1305 closed: reading length: EOF
[UCHGH] INFO: Established secure connection to ZB5HDBC-EQOLHUS-*********-*********-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 128.yyy.yyy.yyy:33588-209.141.59.16:22067/relay-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_$$$$$$$$$_POLY1305
[UCHGH] INFO: Device ZB5HDBC-EQOLHUS-*********-*********-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR client is "syncthing v0.14.43-ds1" named "gix-30224514" at 128.yyy.yyy.yyy:33588-209.141.59.16:22067/relay-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_$$$$$$$$$_POLY1305
[UCHGH] INFO: Connection to ZB5HDBC-EQOLHUS-*********-*********-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 128.yyy.yyy.yyy:33588-209.141.59.16:22067/relay-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_$$$$$$$$$_POLY1305 closed: reading length: EOF
[UCHGH] INFO: Established secure connection to ZB5HDBC-EQOLHUS-*********-*********-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 128.yyy.yyy.yyy:33622-209.141.59.16:22067/relay-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_$$$$$$$$$_POLY1305
[UCHGH] INFO: Device ZB5HDBC-EQOLHUS-*********-*********-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR client is "syncthing v0.14.43-ds1" named "gix-30224514" at 128.yyy.yyy.yyy:33622-209.141.59.16:22067/relay-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_$$$$$$$$$_POLY1305
[UCHGH] INFO: Connection to ZB5HDBC-EQOLHUS-*********-*********-BYEUCEE-6IBQFV5-JWNYLFC-JLOBNQR at 128.yyy.yyy.yyy:33622-209.141.59.16:22067/relay-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_$$$$$$$$$_POLY1305 closed: reading length: EOF
Again thx for super quick response. Here are upgrade attempts on server(beagle) and laptop:
on server beagle: (Ub 16.04)
Fetched 216 kB in 2s (91.4 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
6 packages can be upgraded. Run 'apt list --upgradable' to see them.
blake@beagle:~$ sudo apt upgrade syncthing
Reading package lists... Done
Building dependency tree
Reading state information... Done
>>>>>>>>>syncthing is already the newest version (1.2.2).
Calculating upgrade... Done
------
on laptop (Ub 18.04)
Reading package lists... Done
Building dependency tree
Reading state information... Done
>>>>>>>>syncthing is already the newest version (0.14.43+ds1-6).
Calculating upgrade... Done
So this appears to be a difference by what packages are available in 16.04 vs 18.04. Is there no workaround besides upgrading beagle to 18.04? Also, can you explain the version numbering system(s)?
On beagle it is configured to use apt.syncthing.net, which always provides the latest package. That is not configured on laptop. You can just follow the steps provided on the linked site, you don’t need to upgrade ubuntu.
You can add a custom apt repository (something similar to Ubuntu’s PPA) to your operating systems. Check this link for details: https://apt.syncthing.net/
This repository is maintained by the syncthing team itself and always contains the latest builds (release/stable and candidate versions).
Syncthing started with version “0.2…” and then increased the second number on major updates. The leading “0” generally has a special meaning in semantic versioning, basically meaning that the build is “beta-like” (non-stable API). The versions increased up to the “0.14.x” line and when “0.14.55” was due the developers decided to simply call it “1.0.0” instead and finally drop the leading zero. See the announcement for details.
Versions with appendixes like 0.14.43+ds1-6 are usually made by third party distributors, for example by the official debian repository packagers.
