I’ve made a fresh setup with two new devices (separate to my last topic) with Linux amd64 Syncthing v1.3.3 and got stuck again with no progress while local network connection is running fine.
Device A - has the “master” data which should be copied over to device B which initially had an empty, fresh syncthing folder.
I did not disconnect network or the USB source device. I’ve verified the files can be read properly on the source. Anything I could offer here to diagnose it further?
I’ve never had such problems with Syncthing picking me one after another, so I wonder what or if me has caused this unintenionally??? It just ever ran fine before in every constellation and now - where I need it to copy over a set of regular directories and files - it fails unexpectedly.
Thanks for your patience and help. If required, I come back with more log information. Will let this second “test case” sit as it is if we need it for further diagnosis. (The first I’ve posted before is needed in production).
In your second image for device B I can see for “Letzte Änderung” the deleted “.stfolder”. If this is deleted in real, is clear that this peer can not run. In both peer folders this foldermarker must be available.
Yeah the procedure is the same, just a different package. It will be more interesting for the device where the entry is missing, but it might be useful to run against both.
I’ve ran some stress tests now for a couple of hours doing continuous database updates and checking for this issue in parallel and haven’t found anything on my systems. So it’s not totally systematic at least.
That’s not ok. If you enable the app debug facility, is there also a service which fails to terminate in a timely manner? (that should probably be changed to log at info or even warning level anyway)
