My work laptop was off for the holidays. When I turned it back on this morning, it connected to my home server and synced. Immediately, a sync conflict was generated for every file that has been touched while this machine was turned off. (The Android device got a new device ID during that time because when I upgraded the Android app, I just set it up like a new device so the settings would all be fresh.)
- I have already checked the common sync culprits: no nested folders, no applications that automatically create files, and the Android app correctly sets
ignore permissions. - How can I use the logs/CLI to help troubleshoot this event? I would like to capture the relevant information now since it could be months before it recurs naturally.
- Does the default log level generate a message when the sync-conflict file is created? (The conflict files all have the Android device’s ID appended, but I checked the logs on the Android device and those logs show it syncing the new conflict files, but not creating them.)
- When I use
syncthing cli --home=".\data\syncthing" debug file <folder-id> <file-path>to troubleshoot this problem, do I need to run it on the machine that generated the conflict file? Is there any guide to how to read the output?
In Syncthing generates cnflicts when file only changed on one device, @imsodin recommended the cli and it appears @oleg was able to read this data successfully find his conflict, but I’m still feeling confused as to what I’m looking for.
This is not the first time this has happened. See Many conflicts for a machine that’s been off for a while