Syncthing sync transfer is really slow

So I’ve set syncthing up on two computers as test bench.

Computer #1 - MBP running syncthing 1.18.3 Computer #2 - Virualized Ubuntu running syncthing 1.18.3

I added both locations via discovery server and configured shared folders

From the Mac Client the syncing is like stuck at 1%. I’ve setup five very small .txt files to test the sync

The log files from the Mac Client are below:

2021-10-20 09:16:40 Connection loop
2021-10-20 09:16:40 stats.DeviceStatisticsReference.GetLastSeen: TDKPN7Z-OMBAXMV-PK65ZTP-UAPQDXB-IMJ3ZNT-HSQUVRJ-3BVRZYP-PAN7TQE 2021-10-13 21:16:19 -0500 CDT
2021-10-20 09:16:40 stats.DeviceStatisticsReference.GetLastConnectionDuration: TDKPN7Z-OMBAXMV-PK65ZTP-UAPQDXB-IMJ3ZNT-HSQUVRJ-3BVRZYP-PAN7TQE 2039167353000
2021-10-20 09:16:40 stats.DeviceStatisticsReference.GetLastSeen: 4UGYVUF-5Q52M6L-BAXWG3H-CBNO2TC-HOWE6ZM-NJAZDNT-OTP7FOR-VZUP6AS 2021-10-20 09:15:40 -0500 CDT
2021-10-20 09:16:40 stats.DeviceStatisticsReference.GetLastConnectionDuration: 4UGYVUF-5Q52M6L-BAXWG3H-CBNO2TC-HOWE6ZM-NJAZDNT-OTP7FOR-VZUP6AS 309942875000
2021-10-20 09:16:40 Resolved device TDKPN7Z-OMBAXMV-PK65ZTP-UAPQDXB-IMJ3ZNT-HSQUVRJ-3BVRZYP-PAN7TQE addresses: []
2021-10-20 09:16:40 stats.DeviceStatisticsReference.WasSeen: 4UGYVUF-5Q52M6L-BAXWG3H-CBNO2TC-HOWE6ZM-NJAZDNT-OTP7FOR-VZUP6AS
2021-10-20 09:16:40 Next connection loop in 1m0s
2021-10-20 09:16:41 http: GET "/rest/system/log?since=2021-10-20T09%3A16%3A35.602652-05%3A00": status 200, 2182 bytes in 0.20 ms
2021-10-20 09:16:41 http: GET "/rest/system/status": status 200, 5022 bytes in 0.79 ms
2021-10-20 09:16:41 http: GET "/rest/system/discovery": status 200, 1472 bytes in 0.15 ms
2021-10-20 09:16:41 http: GET "/rest/system/connections": status 200, 1232 bytes in 0.26 ms
2021-10-20 09:16:41 http: GET "/rest/system/error": status 200, 21 bytes in 0.04 ms
2021-10-20 09:16:44 http: GET "https://127.0.0.1:8384/rest/system/ping?": status 307, 76 bytes in 0.03 ms
2021-10-20 09:16:44 http: GET "/rest/system/ping?": status 200, 21 bytes in 0.09 ms
2021-10-20 09:16:49 http: GET "https://127.0.0.1:8384/rest/system/ping?": status 307, 76 bytes in 0.02 ms
2021-10-20 09:16:49 http: GET "/rest/system/ping?": status 200, 21 bytes in 0.08 ms
2021-10-20 09:16:51 http: GET "/rest/system/status": status 200, 5022 bytes in 0.73 ms
2021-10-20 09:16:51 http: GET "/rest/system/discovery": status 200, 1472 bytes in 0.17 ms
2021-10-20 09:16:51 http: GET "/rest/system/connections": status 200, 1232 bytes in 0.37 ms
2021-10-20 09:16:51 http: GET "/rest/system/error": status 200, 21 bytes in 0.12 ms
2021-10-20 09:16:54 http: GET "https://127.0.0.1:8384/rest/system/ping?": status 307, 76 bytes in 0.04 ms
2021-10-20 09:16:54 http: GET "/rest/system/ping?": status 200, 21 bytes in 0.05 ms
2021-10-20 09:16:55 sent 186 bytes to [ff12::8384]:21027 on lo0
2021-10-20 09:16:55 write udp [::]:64200->[ff12::8384]:21027: sendmsg: invalid argument on write to [ff12::8384]:21027 gif0
2021-10-20 09:16:55 addresses: [10.0.1.255]
2021-10-20 09:16:55 sent 186 bytes to [ff12::8384]:21027 on en0
2021-10-20 09:16:55 recv 186 bytes from [fe80::1%lo0]:64200
2021-10-20 09:16:55 write udp [::]:64200->[ff12::8384]:21027: sendmsg: invalid argument on write to [ff12::8384]:21027 en1
2021-10-20 09:16:55 write udp [::]:64200->[ff12::8384]:21027: sendmsg: invalid argument on write to [ff12::8384]:21027 en2
2021-10-20 09:16:55 recv 186 bytes from [fe80::8bd:d29b:e684:66b6%en0]:64200
2021-10-20 09:16:55 recv 186 bytes from 10.0.1.184:64608
2021-10-20 09:16:55 sent 186 bytes to 10.0.1.255:21027
2021-10-20 09:16:55 write udp [::]:64200->[ff12::8384]:21027: sendmsg: can't assign requested address on write to [ff12::8384]:21027 bridge0
2021-10-20 09:16:55 write udp [::]:64200->[ff12::8384]:21027: sendmsg: invalid argument on write to [ff12::8384]:21027 p2p0
2021-10-20 09:16:55 sent 186 bytes to [ff12::8384]:21027 on awdl0
2021-10-20 09:16:55 sent 186 bytes to [ff12::8384]:21027 on llw0
2021-10-20 09:16:55 recv 186 bytes from [fe80::d846:51ff:febf:2e2d%llw0]:64200
2021-10-20 09:16:55 sent 186 bytes to [ff12::8384]:21027 on utun0
2021-10-20 09:16:55 recv 186 bytes from [fe80::7c0:d437:aba0:a2e6%utun0]:64200
2021-10-20 09:16:55 recv 186 bytes from [fe80::1511:81ae:2b8b:da4b%utun1]:64200
2021-10-20 09:16:55 sent 186 bytes to [ff12::8384]:21027 on utun1
2021-10-20 09:16:55 sent 186 bytes to [ff12::8384]:21027 on utun2
2021-10-20 09:16:55 recv 186 bytes from [fe80::cee9:e879:afa5:df20%utun2]:64200
2021-10-20 09:16:55 sent 186 bytes to [ff12::8384]:21027 on utun3
2021-10-20 09:16:55 recv 186 bytes from [fe80::e695:675c:b3f5:121c%utun3]:64200
2021-10-20 09:16:59 http: GET "https://127.0.0.1:8384/rest/system/ping?": status 307, 76 bytes in 0.03 ms
2021-10-20 09:16:59 http: GET "/rest/system/ping?": status 200, 21 bytes in 0.04 ms
2021-10-20 09:17:01 http: GET "/rest/system/status": status 200, 5022 bytes in 0.74 ms
2021-10-20 09:17:01 http: GET "/rest/system/discovery": status 200, 1472 bytes in 0.21 ms
2021-10-20 09:17:01 http: GET "/rest/system/error": status 200, 21 bytes in 0.04 ms
2021-10-20 09:17:01 http: GET "/rest/system/connections": status 200, 1232 bytes in 0.37 ms
2021-10-20 09:17:04 recv 500 bytes from [fe80::2a0:98ff:fe4e:65cf%en0]:52071
2021-10-20 09:17:04 recv 500 bytes from 10.0.1.95:52263
2021-10-20 09:17:04 http: GET "https://127.0.0.1:8384/rest/system/ping?": status 307, 76 bytes in 0.02 ms
2021-10-20 09:17:04 http: GET "/rest/system/ping?": status 200, 21 bytes in 0.07 ms
2021-10-20 09:17:05 http: GET "/rest/system/log?since=2021-10-20T09%3A16%3A40.616075-05%3A00": status 200, 8048 bytes in 0.53 ms
2021-10-20 09:17:07 http: GET "/rest/system/log?since=2021-10-20T09%3A17%3A04.697385-05%3A00": status 200, 233 bytes in 0.10 ms
2021-10-20 09:17:09 http: GET "/rest/system/log?since=2021-10-20T09%3A17%3A05.23491-05%3A00": status 200, 233 bytes in 0.11 ms
2021-10-20 09:17:09 http: GET "https://127.0.0.1:8384/rest/system/ping?": status 307, 76 bytes in 0.02 ms
2021-10-20 09:17:09 http: GET "/rest/system/ping?": status 200, 21 bytes in 0.06 ms
2021-10-20 09:17:09 http: GET "/rest/events?since=2669": status 200, 3 bytes in 60013.10 ms
2021-10-20 09:17:09 http: GET "/rest/events?since=2669&timeout=60": status 200, 3 bytes in 60014.73 ms

I’ll include more of the logs if needbe but they tend to repeat

Looks less like a slow sync and more like not trying to sync at all. A full screenshot of both sides might clarify. (Those logs have some specific debugging enabled and are not terribly useful.)

This ended up being a worthless post on my part – I had not added the device on the other side. Sorry about the bother.

3 Likes

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