I am running syncthing v0.14.45 on a freenas system with version: FreeBSD 8.3-RELEASE-p5 (FREENAS.amd64) #2 r244158M
The version used do work flawlessly before that, no hardware or software change was done to the system meanwhile. The nas is working without issues otherwise.
The system is:
|Platform|Intel® Core™2 Duo CPU E7500 @ 2.93GHz|
|Memory|8037MB|
Since about March 3 2018 syncthing stopped working with the following email being sent to me:
Could someone please help me resolve this, syncthing has become a major factor in my workflow
That’s a bug, I filed it. Try to not enable filesystem watching. Also, you should consider something a little less end of life OS-wise… I’m not sure but there’s a good chance that the “not implemented” panic is because it depends on functionality that just doesn’t exist in 8.3.
This might be happening to me too. I am running FreeNAS-9.3-STABLE-201605170422 and as soon as syncthing auto updated to v0.14.45 it stopped working (My freenas syncthing plugin does not start at all).
I had to install a new instance of syncthing (v0.14.3) and change the Release Url option to a custom JSON that contains only v0.14.44 as the latest version. Once it updates to v0.14.44 everything works as expected (and my freenas syncthing plugin can start and stop on command)
Installed a new instance of syncthing on my freenas instance. I went from v0.14.3 > v0.14.44 > v0.14.46-rc.1 and I still get my original error where the syncthing plugin does not want to start after updating to the latest version.
I’m not sure if my issue is related to the OP. I’ll try to dig from some logs since FreeNas’s plugin/jail system is a blackbox to me.
Edit: @Nikolay_Nenov where are the logs located on a freenas syncthing jail installation?
Just the full output when you run it. Ideally with -no-restart to avoid a bunch failed restarts on top. And be sure to use the right binary, or 0.14.46-rc.1 now. It would be surprising if it still panicked with that build.