I did a sudo apt install synthing=1.6.0, coming from 1.4.1.
The webif showed :
For the following folders an error occurred while starting to watch for changes. It will be retried every minute, so the errors might go away soon. If they persist, try to fix the underlying issue and ask for help if you can’t. Support
movies readdirent: no such file or directory
That folder certainly isn’t missing.
So, I went back to 1.4.1 , all is well.
Then I went from 1.4.1 to 1.4.2 to 1.5.0 without anything to report. Sync works fine.
Until I went to 1.6.0, and again troubles. I grabbed this from syslog
Jun 8 21:41:29 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:29 INFO: Error while trying to start filesystem watcher for folder movies, trying again in 1m0s: error while traversing /mnt/share/media/video/movies/Some folder name: interrupted system call
Jun 8 21:41:31 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:31 INFO: Error while trying to start filesystem watcher for folder tvshows, trying again in 1m0s: readdirent: interrupted system call
Jun 8 21:41:31 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:31 INFO: Error while trying to start filesystem watcher for folder pictures, trying again in 1m0s: readdirent: no such file or directory
Jun 8 21:41:32 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:32 INFO: Completed initial scan of receiveonly folder "surface_adrian_pictures" (fsqtr-adr4a)
Jun 8 21:41:32 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:32 INFO: Completed initial scan of sendonly folder "3D" (mmaf6-gkdez)
Jun 8 21:41:37 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:37 INFO: Completed initial scan of receiveonly folder "surface_adrian_documents" (t4zjm-sv7sc)
Jun 8 21:41:39 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:39 INFO: Detected 3 NAT services
Jun 8 21:41:47 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:47 INFO: quic://0.0.0.0:22000 detected NAT type: Port restricted NAT
Jun 8 21:41:47 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:47 INFO: quic://0.0.0.0:22000 resolved external address quic://213.219.146.215:22000 (via stun.syncthing.net:3478)
Jun 8 21:41:58 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:41:58 INFO: Joined relay relay://95.102.55.116:22067
Jun 8 21:42:03 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:42:03 INFO: Completed initial scan of receiveonly folder pictures
Jun 8 21:42:16 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:42:16 INFO: Completed initial scan of sendonly folder movies
Jun 8 21:42:30 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:42:30 INFO: Error while trying to start filesystem watcher for folder movies, trying again in 2m0s: readdirent: no such file or directory
Jun 8 21:42:32 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:42:32 INFO: Completed initial scan of sendonly folder tvshows
Jun 8 21:44:30 syncthing syncthing[126]: [JHCJA] 2020/06/08 21:44:30 INFO: Error while trying to start filesystem watcher for folder movies, trying again in 4m0s: readdirent: no such file or directory
I don’t really know where to start logging/troubleshooting for this one?
The folders are a mounted cifs share. The system doing the sharing is an LXC hosted by Proxmox. Syncthing is also an LXC on the same Proxmox.
Can you pinpoint which thing causes the problem? That is, does Syncthing work under proxmox with local folders? Does it work outside proxmox with a folder on cifs? Or some other relevant detail about your system that might be unusual.
Yeah the problem seems unpredictable, probably because it is timing related (interrupt happing at an unexpected time). The above narrowing down would still be useful.
I am getting the same problems in the docker container of version 1.6.1
The go version in there should probably be the correct one, so maybe it is not go/os related?
I also have a CIFS share, probably that is causing the problem then?
These kind of errors may become less frequent with go 1.15 again:
Packages os and net now automatically retry system calls that fail with EINTR . Previously this led to spurious failures, which became more common in Go 1.14 with the addition of asynchronous preemption. Now this is handled transparently. Go 1.15 Release Notes - The Go Programming Language