syncthing: Syncing stuck on XX% on one device, despite the synced files are all ok and checksums match on all devices involved.

What happened?

I was syncing a new device (Windows fresh install) to my pool of devices, and synchronization went well but at the end on that new device Syncthing shows 26% syncing progress and it is completely stuck since 12h+. All other devices show status synced (up to date). The checksum of all files within multiple directories match, so it means that desired content is properly synced, but Syncthing says something else. I tried rescaning, restarting etc. nothing changed. It is just completely stuck.

In the log I see a lot of those entries related to the affected directories and device reporting stuck syncing:

[XXXXX] 2024/03/24 22:46:48 INFO: Puller (folder “adsfasdfasdf” (uuuuu-uuuuu), item “asdfasdfasdf”): syncing: no connected device has the required version of this file … [XXXXX] 2024/03/24 22:46:49 INFO: Folder “adsfasdfasdf” (uuuuu-uuuuu) isn’t making sync progress - retrying in 2m10s.

I think the same thing happen to me we another device few hours before, but I was not paying sufficient attention and I just recreated sync pair and resynced one affected folder. But then data transfer was not completed and half of the files were missing on the newest device. Now I have 3 affected folders and a lot of more data which is actually synced.

Also what is worth to mention, there should be some kind of better error message maybe, because it is not possible to reattach missing source device because there is no more, plus only viable info can be found buried in log files.

image

More info on previous sync stuck problem: https://forum.syncthing.net/t/missing-half-of-the-photo-files-but-the-status-shows-100-completed-on-src-and-target/21841/3

Syncthing version

v1.27.4

Platform & operating system

Windows 11 PRO x64, Linux Ubuntu 22 x64

Browser version

Firefox 124.0.1 (64-bit)

Relevant log output

[XXXXX] 2024/03/24 22:46:48 INFO: Puller (folder "adsfasdfasdf" (uuuuu-uuuuu), item "wsugfuxtfc756q"): syncing: no connected device has the required version of this file
..........
..........
..........
[XXXXX] 2024/03/24 22:46:49 INFO: Folder "adsfasdfasdf" (uuuuu-uuuuu) isn't making sync progress - retrying in 2m10s.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 2
  • Comments: 37 (5 by maintainers)

Most upvoted comments

I will add that doing a rescan on the folder or restarting Syncthing does not help. However, running Syncthing with the “–reset-database” parameter clears the error.

No, this is a real issue apparently. At least some proper logging in the code should be provided. If the app stuck for any reason, I would like to see that reason in the log. Not to play the guess me game.

The single thing alone - one device reporting synced status and another reporting sync in progress (stuck) status is a sufficient reason for me to add some more logging and/or render the sync progress on both as failed.

This issue seems to just absorb all “things aren’t syncing” problems people experience, regardless of setup or root cause. I’m closing as not actionable. Most people should probably turn to the forum for some troubleshooting help. Any particular bugs found will get individual tracking issues.

There is an option in the app settings to do a database reset.

It looks like I didn’t look very well, thank you so much, I managed to solve the issue.

I will add that doing a rescan on the folder or restarting Syncthing does not help. However, running Syncthing with the “–reset-database” parameter clears the error.

Is there anyway to do the same thing on Android, unfortunately I couldn’t find anything.

There is an option in the app settings to do a database reset.

Same here:

  • From my device I see : Éléments non synchronisés 2 élément(s), ~9,63 MiB
  • From the other device I see it’s 100% in sync.

I checked the sha1sum of the two elements, they are the same.

Also I did not modified those files since like 2018, so that’s strange seeing this popping right now.

My device is running syncthing 1.27.2~ds4-1 (on Debian Trixie), the other one is running syncthing 1.19.2~ds1-1+b4 (on Debian bookworm).

I grepped the out of sync files in the logs: nothing:

$ journalctl --user -u syncthing --grep sh3d
-- No entries --

(yes the two “out of sync” files are sh3d files).

In my side I have a .stignore containing:

(?d).venv
.envrc

in the remote there’s no .stignore file.

I don’t know where to gather more info from here.

Same here, Syncthing v1.27.5, Linux (64-bit Intel/AMD): Device A (send only folder) → Device B (receive only folder) (Browser-)GUI on says syncing (99%, 1 item out of sync), (browser-)GUI on B says everything up to date. Complained item exits on both devices with same sha512sum.

I think I’m seeing the same issue. 3 devices (2 Linux, 1 Windows 11) all running V.1.27.6. Each device says it is synced and up to date, but one device constantly shows another device as “Syncing (50%, 8.22GiB)”.

I observe that the description of the out of sync remote says: “Out of Sync Items 2,651 items, ~8.22GiB”

If I click on the items link, the “Out of Sync Items” window is empty. Perhaps this is a clue.

I have reproduced the issue for the 2nd time. I created fresh VM with Windows 11 PRO x64 and left it for the night to synchronize with 2 devices from my pool. The effect is the same - device C (this newest) got stuck with device A (the oldest one). Please see attached pictures. What I see is that on picture A, the device A has a remote with the name of A but it should be C - WTF happen here?!?!?!

I will preserve the whole Syncthing configs with logs from A, B and C if anybody wants to ask for more details, maybe I will be able to dig through it.

Explanation: A - The oldest one B - New one I have added few days ago C - Test device

What I see is that the newest device C got the same name as my device A somehow. And probably this is why this thing got stuck.

Please tell me what should I look for in the logs to help fixing this issue. I can even run that for the 4th time if it helps but it is boring 😉

A

B

C

I have removed the sync directory from the Syncthing only from the newest device and readded it again with default settings except Alphabetic download order (pointing to already synced data folder, entering the desired directory ID) and after the scan Syncthing said that everything is synced OK. Again I have checked the files checksums (calculated + verified on all additional devices added to my “master” node) and all the data match.

I guess there is some kind of a bug in Syncthing and it happen already twice for me. I will probably setup a VM for testing purposes and I will try to make another full sync just for my curiosity. If there is any advise what shall I check during that process, please let me know. One think which may be a culprit is that the one directory has approx 200_000 super small files and maybe because of that Syncthing got stuck also with other directories, IDK. This is super weird.