In this post I was worried that syncthing destroyed my files:
Now I’m more confident that it didn’t happen, but I still find myself in the position of trying to figure out what the heck syncthing is doing sometimes. The GUIs help: I can see if a folder is out of sync, by how much, and even the file transfer progress (to a certain extent). But that’s when I have the GUI and that doesn’t provide me with an history of changes.
In the above post, I was told to use the audit commandline flags but that prove to actually be quite difficult to use. It outputs JSON which is nice for programmers and admins (like me) but really not that nice for more novice users (who might not know how to parse JSON).
We output a lot of logs by default, for example I frequently see things like this:
jan 14 09:30:27 angela syncthing[6435]: [72RXH] INFO: Connected to myself ([REDACTED]) at 172.17.0.1:22000-192.168.0.117:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 - should not happen
jan 14 09:30:33 angela syncthing[6435]: [72RXH] INFO: Connection to [REDACTED] at 192.168.0.117:22000-192.168.0.153:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 closed: read timeout
which is… interesting, but not necessarily everything I want to know. (I’ll also note this contains PII which we should generally be careful about, but I guess that’s expected…)
So what I would like syncthing to do, by default, is say things like this:
- transferred file foo.txt from remote X
- transferred file bar.txt to remote X
- deleted file bar.txt to sync with remote X
… basically. I know that it could mean a lot of output on first syncs, but maybe the output could be rate-limited?
This is important to deal with situations like the thread above, but it’s also helpful in other cases. I just setup syncthing on my Kobo ebook reader (!) which is really awesome (!!) and it kind of works. One problem I often have is the CPU is somewhat slow on there, so sometimes it looks like syncthing is not doing anything. I opened a logfile (which has already grown to 56MB, btw, something for another thread), but it doesn’t really tell me much. I could tell it started scanning a folder, which took several minutes, so that might be what happened. But it didn’t tell me when it transfered that ONE file I wanted to have on that thing. I just had to hit refresh in the file browser repeatedly, which was a frustrating user experience.
Having file transfer updates would also help me see what’s going on in my desktop, since there I run syncthing in the background. Then I could just tail the journalctl logs to see what’s going on.
Thanks!