Appdata synced without issues, but on my big data folder it has been stuck for a few hours now, restarting the service did not help either. I am confused why it marks the device as “Up to Date” as well…
Seems somewhat related to Untrusted host (encrypted), stuck syncing from another trusted host - #3 by FingerlessGloves
Still no success, after multiple restarts and readding the folder
What do the logs say?
2022-11-22 18:26:32 Ready to synchronize "data" (data) (receiveencrypted)
2022-11-22 18:26:32 Completed initial scan of receiveencrypted folder "data" (data)
2022-11-22 18:26:32 Device 5HJMFOJ folder "data" (data) has mismatching index ID for us (0x83390A9CEE793CB9 != 0xE2C49E7D7124553F)
2022-11-22 18:26:32 Device 5HJMFOJ folder "data" (data) has a new index ID (0x753DB9957B4613E8)
...
2022-11-22 18:26:32 Listener for quic//0.0.0.0:22000: unknown address scheme ""
2022-11-22 18:26:32 Ready to synchronize "data" (data) (receiveencrypted)
2022-11-22 18:26:32 Restarted folder "data" (data) (receiveencrypted)
2022-11-22 18:26:32 Completed initial scan of receiveencrypted folder "data" (data)
...
2022-11-22 20:50:57 Sharing folder "data" (data) with THWBCSV-... (vouched for by introducer 5HJMFOJ-...)
2022-11-22 20:50:57 Listener for quic//0.0.0.0:22000: unknown address scheme ""
2022-11-22 20:52:46 Folder "data" (data) isn't making sync progress - retrying in 2h27m0s.
2022-11-22 20:52:46 Ready to synchronize "data" (data) (receiveencrypted)
2022-11-22 20:52:46 Restarted folder "data" (data) (receiveencrypted)
2022-11-22 20:52:55 Completed initial scan of receiveencrypted folder "data" (data)
2022-11-22 21:10:09 Connection to BA2RCUU-... at 172.16.0.238:22000-172.16.0.156:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 closed: read timeout
2022-11-22 21:23:18 Established secure connection to BA2RCUU-... at 172.16.0.238:22000-172.16.0.156:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
I thought it could be the memory, that the 8GB of the machine do not suffice to build the file list, but barely 1GB is in use.
I would appreciate hints for a quick fix as I would ideally have this work within the next few hours.
Need more of the log, but from what’s shown, there are at least a couple of issues…
Seems important, but I don’t know enough about it to offer additional input.
You have a syntax problem in the Sync Protocol Listen Addresses field. It’s supposed to be in URI format: quic://0.0.0.0:22000
The retry timer above explains the extended delay.
Device BA2RCUU has a network or some other issue because it didn’t respond before timing out and then finally succeeding:
Besides the networking issues above, a relatively large number of files and directories + encrypting files + multiple hosts syncing to 6CQVVE puts a lot of load on 6CQVVE.
5HJMFO/elephant-arch can say “Up to Date” because it’s only one of multiple hosts syncing with 6CQVVE. For example, if “Butterfly” is out of sync, 6CQVVE could be preparing to send it changes received earlier by “elephant-arch”. Also, every time Syncthing is restarted on 6CQVVE it needs to scan everything again to see if anything changed while it was offline. Restarting multiple times usually increases the sync time rather than speeding it up.
Alright, thanks for the hints 
Gladly, it finally started syncing now, after many hours of idleness ^^
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.