WebGUI of Syncthings says that everything is ok. It gives status synchronizing 0% on Atom side and on Quad it gives first synchronizing 0%, but after some times it shows disconnected.
On Quad after disconnection SYncthing show wrong CPU Utilization… it gives about 300% CPU, but top is showing that 0% of CPU is used by Syncthing.
What to change in Syncthing to return to normal running?
Should I remove all indexes folder or something like that?
Connection to ID closed: ping timeout
Established secure connection to ID at ip:port-remoteip:port
Device ID client is "syncthing v0.10.9"
Device ID name is "Name"
INFO: Connected to alreadyt connected device
And nothing more for 5 hours, nothing gets send.
But on second server there are a lot of logs:
Puller .doc hash mismatch x 10
Puller .dwl hash mismatch
Puller ... pull: connection closed
Connection to ID closed: ping timeout
Established secure connection to ID at ip:port - remoteip:port
Device ID client is "syncthing v0.10.9"
Device ID name is "SecName"
TLS handshake read tcp ip:port: connection reset by peer
Puller (folder "Name"), file /volume/.../*.tmp : pull: no available source device
AND a log of pull: no available sources and second server is working like nothing happened,
WebGUI on both server shows that everything is okay, on first server is showing that everything is synced, second server showing about 80% of synced items and nothing happens.
And true is that syncing is not working at all after connection reset by peer.
are there any news concerning this issue? I have a similar problem trying to setup an initial simple folder sync with my Ubuntu and my two android mobile devices. Connected via wifi in my private LAN.
All went well in terms of connection and device visibility until I shared the desired local folder with the two devices. Suddenly they are not able to connect to each other and syncing does not proceed.
The terminal log of the Ubuntu machine repeatedly states:
[VMKXK] 12:31:01 INFO: Established secure connection to [Device-ID] at 92.168.1.210:22000-192.168.1.209:35025
[VMKXK] 12:31:01 INFO: Connection to [Device-ID] closed: read tcp 192.168.1.209:35025: connection reset by peer
What could be the reason for this behaviour? Any hints would be highly appreciated.
Cheers,
Nix
I don’t think you should file issues for support, I think you should file issues for bugs.
You should use the forum for support.
As I said, check the logs/console output on the other peer, as it might give you clues why it’s disconnecting.
At the point you start syncthing, it prints the version, make sure that both versions are 0.10.x or 0.11.x
Edit: I closed your issue, the Android version (as it says in settings) is still at 0.10, hence incompatible with 0.11.
To my understanding it was/is an actual bug. And I didn’t do it for support in the first place, but to raise awareness to this issue. So far I haven’t stumpled upon any piece of information that there are incompatibility issues between protocol versions. Do you have any suggestions in that case? Reinstall an earlier version on the linux box?
Maybe I am misreading something, but isn’t
… make sure that both versions are 0.10.x or 0.11.x
and
I closed your issue, the Android version (as it says in settings) is still at 0.10, hence incompatible with 0.11.
not somewhat contradictory? Don’t mean no offence, but I’m not getting it. I mentioned the devices are at v0.10.x and v0.11.0, respectively. You think these versions are incompatible or not?
As I stated above, the only “clue” i am getting is from my ubuntu machine - the connection is reset by the mobile peers. Not any information why it is doing it. It might help me to understand, how I might get similar information on the mobile devices. Do you happen to know that by chance?