Syncthing keeps getting stuck (95%, 0 B Left)

I am syncing a server to another server as an off site backup. Syncthing is configured as share only for the master server. Check for changes and ignore permissions are enabled. No manual changes are being made to the backup server.

Everything will be fully synced, but then every couple weeks something will break, and it will say “95% Synced, 0B”. The out of sync files are always files that recently got added. Rescanning both servers or restarting syncthing doesn’t fix it.

The only way I have found to fix this is to delete the share device on each server, restart syncthing, re-add/re-share, and then have it recalculate from scratch. It will then report 100% again and be back to normal for a few more weeks.

Why is this happening?

1 Like

You should check for the cause of not being to sync on the other side.

There are no errors on the other side (receiving server). Global/Local state match, and the share claims to be up to date and fully synced on the receiving server. Yet, on the master server it still says 95% syncing 0 bytes.

Rescanning both shares on both servers, same thing. I suspect this is some sort of WebUI display bug. I have tried deleting cookies, forcing a refresh, and checking in another browser. The only thing that fixes it is deleting the share under remote devices on both ends, and then re-sharing.

EDIT: Upon further inspection, the files it’s claiming are out of sync are files that were deleted from the master server and then deleted from the backup server as a result. The files aren’t there anymore on both servers, but on the master server’s end it is claiming they still need to be deleted from the backup server. Still thinking this is a WebUI display bug of some sort.

1 Like

Can you post screenshots of the folder in web ui from both sides?

If folder status is up-to-date on both sides, that’s what the state is - the remote completion is in a sense just “informational”. Still of course it should be accurate. Reports that a deletion is not being recognized in the remote section came up before, but I still have no clue as to how it happens. If it is the same as the reports I remember, it is not an UI issue though - that’s anyway unlikely. Running Syncthing with -reset-deltas fixes it and that should be easier than re-adding folders. I need to try and dig up all these reports, maybe on re-reading all of them something stands out.

You could also post the output of GETing the /rest/db/file endpoint on both sides for a file in question (see, something like curl -X GET -H "X-API-Key: yourapikey" 'http://localhost:8384/rest/db/file?folder=folderID&file=pathRelToFolderRoot').

1 Like

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