It shows that its actively syncing files but nothing is happening.
and the folder on all systems shows that its fully synced.
Here are some screenshots
I noticed this issue (was running beta8 at that point, upgraded to beta10 and the issue stayed) restarting the beta instance also has no effect.
I see no meaningful / any errors in the docker container logs. (all instances are docker containers v1.29.5)
if you need any other logs / files from me let me know.
I tested and the sync seems to still work.
added a file on the source machine (1 machine has folder as send only, the others as receive only) and sync still works.
There was some database damage due to a bug in an earlier beta; if you ”touch” any of these files, do they sync? If not, I’m more interested and would like to look closer, can provide some database commands.
Just checked and it seems that all the files in the list are files that by now have been deleted.
(expected behaviour off frigate (frigate is an NVR where I have auto-cleanup enabled)
although the list shown in my previous post has grown in size (file-count and total size)
While checking though I noticed that the beta instance has more files that the source and the same for another normal instance.
folder settings
source (send only)
target (receive only)
beta (receive only)
“Ignore delete” is disabled on all these folders
I can’t disable the nvr for security reasons so there will still be changes in files. But I’m not touching anything Syncthing related in case you want me to try something specific.
Upgraded 2 devices to v2 so far, one went smooth the other one is stuck out of sync now for 7 out of 10 folders. The migration itself seemed to be successful.
no infos about why they are out if sync in the log or the gui, log just says
[4XXFU] 2025/04/22 13:22:11.280030 folder.go:438: INFO: Folder cloud isn't making sync progress - retrying in 8m17s. for the out of sync folders. GUI switches between “Preparing to Sync” and “Out of Sync” when it retries.
Another thing that seems weird is that syncthing sends >100MB to both remote devices that share most of the folders, this seems to repeat after every restart of syncthing.
What also seems wrong is that index-v0.14.0.db still existed with some files in it and after a restart. Syncthing v2 complained with the following lines and only started again after removing the old index folder.
[start] 2025/04/22 13:05:57.371173 utils.go:193: WARNING: Old-style database present but already migrated at 2025-04-22 12:13:06.858636008 +0200 CEST; please manually move or remove /home/alex/.config/syncthing/index-v0.14.0.db.
[start] 2025/04/22 13:06:02.379808 main.go:497: WARNING: Error opening database: openbase (PRAGMA journal_mode = WAL): database is locked
The following log file should contain one loop of trying to sync one of the folders that is stuck with “model” debug enabled: st-log.txt (5.1 KB)
I will leave it in this state for now so I can provide additional data if you need anything.
You can mimick SyncTrayzor with the Windows Task Scheduler. I have a task on my NAS that runs every hour and another task on my laptop that runs at log on and startup. There’s no tray icon, but this can be mimicked with a bookmark in whatever browser you use to the local ip of Syncthing. I’ve been running this configuration for years with little to no issues.
Hi, calmh, syncthing becomes better day after day, this is very cool.
But you know, the performance of SQLite is not very good and often show busy errors, I’m wondering that do you have plan of use PGSql or MySQL replace SQLite in future?
I add 4 folders to monitor 4 different servers’ source data folder in destination server. So, maybe there are many files are sync at the same time. There is no any other logs except this. Our OS is Windows 10.
About last question, do you mean that if I can accept a paid support?
I notice you’re running a build of your own using the Go-translated version of SQLite. It would be good to see if you get the same with our “official” builds.
Hi, as you can see, syncthing record logs into a single log file when it’s running, if syncthing keep running, the log file will be larger and larger and will be difficult to be open and use in future.
So, I want to know could you optimize this way to that save every day’s log to new log file and save them to a folder (e.g. audit-log-files).
Plus, support to set the valid days of audit-log-file and if it was overdue, syncthing will delete it automatically.
or reset delta indexes everywhere.
Thank you for your tip. I will try it.