This happens about three times a week. Seems it happens when I actively working on a file, even as I save it and keep working on it.
On PC, GUI shows the phone is stuck at 99% 512B. The file seems to sync OK to the phone though when I view it.
If I have to guess, from looking at the output in shell, this is because of NAT restriction (I do not have ports open for Syncthing). I haven’t had ports open for Syncthing previously either, so something else is going on,
Here’s the output (note - I took out the device ID. I work with a VPN atm, but this is an issue with or without)
07:27:38 INFO: Device Z**** client is “syncthing v0.14.48-dirty” named “Pixel 2”
[V4TT6] 07:27:42 INFO: kcp://0.0.0.0:22020 detected NAT type: Port restricted NAT
[V4TT6] 07:27:42 INFO: kcp://0.0.0.0:22020 resolved external address kcp://98.143.145.254:22020 (via stun.internetcalls.com:3478)
[V4TT6] 07:27:57 INFO: Joined relay relay://107.150.6.122:8080
[V4TT6] 07:28:05 INFO: Established secure connection to Z**** at 192.168.50.144:50916-192.168.50.244:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305)
[V4TT6] 07:28:05 INFO: Replacing old connection 10.8.8.27:37316-192.99.59.139:443/relay-client with 192.168.50.144:50916-192.168.50.244:22000/tcp-client for Z****
[V4TT6] 07:28:05 INFO: Connection to Z**** closed: reading length: read tcp 10.8.8.27:37316->192.99.59.139:443: use of closed network connection
[V4TT6] 07:28:05 INFO: Device Z**** client is “syncthing v0.14.48-dirty” named “Pixel 2”
I do not see that (see picture). Only have out of sync items, which is indeed clickable – but it only shows me which items have the problem, not much more info there.
OK I found out what the issue was (at least this time) and it’s not Syncthing fault. The app on the sending device, Emacs in my case, had the files open. This is not always the case because Emacs can be a bit weird about when sometimes a buffer is closed and when it’s really closed. Got out of the app, and it synced right away.
I thought though that Syncthing could sync the saved files anyway… But I’ll figure it out there are ways around that.
Thanks for clarifying, next time I’ll use on the right side to troubleshoot.
I have the same thing (3 items, 384B) on my Mint 18.3 box, and the out-of-sync items are all folders, with an empty “size” column, claiming the “Mod Device” is the other computer (running OSX). The OSX computer says everything is up to date.
Is this a bug? I have removed / re-added these folders on both sides in Syncthing, and I’ve closed all running applications on both sides. Note last time when I removed / re-added the folder on the Mint side, it stalled out with one folder instead of 3. Prior to that, there were many folders stalled out.
In any case, what does it even mean for a folder to be out of sync like this? Does it mean all of its contents will not sync, or something more benign?
Failures are per file. If you are looking at remote out of sync item, you will not known what the cause is. The cause is only shown to the local device. If you are still having issues, please post screenshots.
Syncing is fine, if the folders (as opposed to remote devices) on both sides are up to date. Even if there are failed items, pulling and scanning will still happen and everything that works, is synced.
Do you really have 3 items, 384B in the status but only dirs, without a size in the list? That would be very weird. Screenshots will help
