I am new to syncthing, trying to use it to transfer large database dumps between two sites ( rsync via VPN is painful ).
so i installed syncthing on two devices.
first ( seed ) is a VM with 4 cores and 4GB RAM, seems to idle.
second ( receive ) is a physical machine with 24 Cores and 16GB RAM.
On the seed side i have 1Gbit Internet, while on the receiving side its only a 10Mbit sdsl line, countryside. thats why rsync via VPN just wont make it.
The databasedump consists of 4 files, largest file is 128GB ( its a 1.4TB database ).
i imagined the dump to transfer in about 4-5 days, working away in the background. But it seems that i have issues that the machines just dont connect to each other… but the internet is stable. slow but stable.
i read that it needs a lot of cpu and ram for transferring large files but i ran HTOP on both machines, both idle, just employ one core and almost no RAM.
Double check that either machine isn’t a very old version. Double check that incoming traffic to port 22000 on 80.190.133.146 isn’t blocked by the firewall.
my junipers are cool, i am using a relay server anyway so its only outgoing on both sides. or so i understood… would not need a relay otherwise?
I also start transferring for a while until it stalls.
But my versions differ… damn.
i will update the old version on the sending side and try again.
Now both versions are up to date.
now it does not run at all anymore. before it worked at least a bit.
i can remember when i used it 1 year ago 8 thats why one side was old ) to another receiver in the same net as the new one, it worked like a charm…
Adresse dynamic
quic://192.168.30.53:22000
context deadline exceeded (11:15:04)
quic://192.168.30.57:22000
Handshake did not complete in time (11:15:04)
quic://62.154.246.62:1070
Handshake did not complete in time (11:15:04)
quic://62.154.246.62:10867
Handshake did not complete in time (11:15:04)
quic://62.154.246.62:11494
Handshake did not complete in time (11:15:04)
quic://62.154.246.62:13528
context deadline exceeded (11:15:04)
quic://62.154.246.62:19788
context deadline exceeded (11:15:04)
tcp://62.154.246.62:7723
i/o timeout (11:15:54)
quic://62.154.246.62:22000
context deadline exceeded (11:15:04)
quic://62.154.246.62:22690
context deadline exceeded (11:15:04)
quic://62.154.246.62:27928
context deadline exceeded (11:15:04)
quic://62.154.246.62:28013
context deadline exceeded (11:15:04)
quic://62.154.246.62:29255
context deadline exceeded (11:15:04)
quic://62.154.246.62:29336
context deadline exceeded (11:15:04)
quic://62.154.246.62:29626
context deadline exceeded (11:15:04)
quic://62.154.246.62:2965
Handshake did not complete in time (11:15:04)
quic://62.154.246.62:29945
context deadline exceeded (11:15:04)
quic://62.154.246.62:30734
context deadline exceeded (11:15:04)
quic://62.154.246.62:3075
Handshake did not complete in time (11:15:04)
quic://62.154.246.62:32085
Handshake did not complete in time (11:15:04)
quic://62.154.246.62:3333
Handshake did not complete in time (11:15:04)
quic://62.154.246.62:3771
context deadline exceeded (11:15:04)
quic://62.154.246.62:4457
context deadline exceeded (11:15:04)
quic://62.154.246.62:5332
context deadline exceeded (11:15:04)
quic://62.154.246.62:5787
context deadline exceeded (11:15:04)
quic://62.154.246.62:5820
context deadline exceeded (11:15:04)
quic://62.154.246.62:7431
context deadline exceeded (11:15:04)
relay://164.90.190.7:22067
tcp://192.168.30.53:22000
i/o timeout (11:15:54)
tcp://192.168.30.57:22000
i/o timeout (11:15:54)
tcp://62.154.246.62:10574
i/o timeout (11:15:54)
tcp://62.154.246.62:7032
i/o timeout (11:15:54)
tcp://62.154.246.62:11400
i/o timeout (11:15:54)
tcp://62.154.246.62:11656
i/o timeout (11:15:54)
tcp://62.154.246.62:11808
i/o timeout (11:15:54)
tcp://62.154.246.62:12530
i/o timeout (11:15:54)
tcp://62.154.246.62:12791
i/o timeout (11:15:54)
tcp://62.154.246.62:14598
i/o timeout (11:15:54)
tcp://62.154.246.62:16103
i/o timeout (11:15:54)
tcp://62.154.246.62:16763
i/o timeout (11:15:54)
tcp://62.154.246.62:16963
i/o timeout (11:15:54)
tcp://62.154.246.62:17867
i/o timeout (11:15:54)
tcp://62.154.246.62:18864
i/o timeout (11:15:54)
tcp://62.154.246.62:21521
i/o timeout (11:15:54)
tcp://62.154.246.62:22000
i/o timeout (11:15:54)
tcp://62.154.246.62:23951
i/o timeout (11:15:54)
tcp://62.154.246.62:25692
i/o timeout (11:15:54)
tcp://62.154.246.62:26177
i/o timeout (11:15:54)
tcp://62.154.246.62:27119
i/o timeout (11:15:54)
tcp://62.154.246.62:30691
i/o timeout (11:15:54)
tcp://62.154.246.62:31055
i/o timeout (11:15:54)
tcp://62.154.246.62:3876
i/o timeout (11:15:54)
tcp://62.154.246.62:4951
That shows a shitload of NATed addresses, and zero relays. Your Junipers may be very cool indeed, but if you’re not going to allow direct connections you’re better of disabling NAT traversal on the Syncthing side, and you should make sure relaying is enabled.
seems to work now after a while…
i have 3% of 148GB now.
these /var/log/syslog entires here are gone
… syncing: no connected device has the required version of this file
… Failed to sync 4 items
only getting nice messages now like
Dec 18 10:41:05 stor0 syncthing[6332]: [FWRUO] INFO: quic://0.0.0.0:22000 resolved external address quic://62.154.246.62:20812 (via stun.syncthing.net:3478)
and it does something, so it looks quite good…
i will give a shout if it works when it trasferred, will take a few days.
edit: seen your post with the nat traversal and relay just now, i will look into it, thanks.
i cant at the moment allow direct connections, i would have to put one machine in a DMZ. or transfer via the IPSEC tunnel, but that seems too slow for me… but maybe i try that.