I have two Syncthing nodes which are connected, with files needing sync, but bytes aren’t moving. Pointers on how to get things moving would be appreciated.
2020-09-18 17:22:52 Established secure connection to YY4ECWC-SEM7A2I-5RZ26GT-ZQTKARQ-TJ6WLGK-E4ZVWDT-RXJXVE3-UUWMNAA at 192.168.8.10:22000-192.168.8.203:49561/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
2020-09-18 17:22:52 Device YY4ECWC-SEM7A2I-5RZ26GT-ZQTKARQ-TJ6WLGK-E4ZVWDT-RXJXVE3-UUWMNAA client is "syncthing v1.9.0" named "GACDTL01KK4056" at 192.168.8.10:22000-192.168.8.203:49561/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
Node 1 says there are 15 items to sync. Node 2 says there are 344 items to sync. Both say the upload and download rate is 0 B/s.
I’d prefer not to upgrade ST on the Ubuntu node unless we know it would fix the issue. I installed it with apt, and I’d have to convert it to a manual install or mess with my source repository settings.
If I watch it for about 5 minutes, it will briefly switch to an upload and/or a download rate of 6 bps. With 4 gig to transfer, that’s going to take an ‘undesirable’ amount of time.
You can enable model debugging to see what it’s doing.
It’s likely still exchanging the indexes.
Is this running on some silly underpowered devices?
And yes, you should update, I don’t think we’d be going deep into understanding of why this is happening just because of how much of an outdated version you are using.
I do sync some underpowered devices, but these aren’t them. These devices are on the same LAN and ping with 10K frames at 2 ms, so network shouldn’t be the problem.
I suspect the Windows box of being the problem because the Linux box successfully syncs with 5 different machines with no problem. The Windows box also took a pushed software update recently, where the Linux box has been static.
Here’s 5 minutes of model debugging on the Windows box. If you don’t see anything, I might try rebuilding the index on the Windows box.
Is there a step-by-step on migrating an apt-installed Syncthing to a manual install?
That’s the sticking point for me to upgrade. It isn’t a philosophical objection to an upgrade. If I saw a simple upgrade option, I’d take it.
My apt-installed Syncthing is capped at its current version because that’s the version that goes with Ubuntu 18, and that’s what I’m running on the server. (And this server has enough funky hardware that upgrading to Ubuntu 20 is a month-long effort.)
Ouch! I found out why sync stopped. The database was corrupted. Then I rebuilt the index and sync resumed. Then it stopped again. The database was corrupt again.
Then I found out why my DB kept getting corrupted – the underlying disk has a problem. Call it a hardware problem.