-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syncthing: accept: function not implemented #5289
Comments
/cc @acolomb |
Sorry I can't take a closer look at the moment. But I remember seeing some of these messages on the Syncthing forum, so please search there. If I remember correctly, it has to do with the old kernel or glibc version on that device no longer working with the newer Go version that Syncthing is compiled with. That's a decision from the Go maintainers, not Syncthing. So probably your best bet is to install an older version and disable any further upgrades. |
Here's the issue with more details: syncthing/syncthing#8325 |
So would using DSM7 fix this? Then I propose that as the solution for now. If not this might be another candidate to use bubblewrap for. |
If there is a DSM7 build available for these old devices, and it includes a newer glibc, then yes it should help. I haven't understood what bubblewrap is or does yet. Care to give an overview? Or is there something in the Wiki? |
Here's how I was able to get Syncthing fixed on my DS212J (which is running DSM6):
|
Very good summary, thank you! |
I think bubblewrap is used by flatpack to create a lightweight container around an application. Conceptually kinda like docker if you like. Basically we would be bundling our own glibc and system libs from say Debian. Unfortunately the method used requires root and may require the user to do some manual things to their NAS. Alternatively we can just mark the older platforms as not supported. |
@publicarray Hm... So bubblewrap doesn't sound like a viable alternative to me, if it needs any tinkering beyond just installing the package. I'd think trying to convince the Golang devs to bring back the previous implementation as a fall-back for older glibc would be more worthwhile. Or just wait until all that old hardware has disappeared, which is of course not a nice solution. But in the end, someone who cares about the problem enough needs to put in the required effort, and for myself, the importance : effort ratio is still much too low because I have production systems where the current version just works :-/ Marking other platforms as unsupported sounds reasonable, so users will just not get any further SPK updates. But it won't affect the internal updater. If there are two versions for a package, with non-overlapping arch lists, will the Package Center choose the latest one which supports the current platform? Then we could provide a dead-end alternative package which forcefully disables updates on older archs. |
This is now fixed upstream in Go; see golang/go#57333 It was backported to Go 1.18.x and Go 1.19.x branches (so will be in Go 1.18.10 or Go 1.19.5), and will be included in the upcoming Go 1.20 release in a couple months. |
This issue should be resolved by syncthing/syncthing#8747. How do we get the latest version on Synology? |
Is this a new Bug?
Package Name
Syncthing
Package Version
1.20.0-26
Device Model
DS413j
Device Architecture
ARMv5
Firmware Version
DSM 6.2.4-25556
What happened?
I noticed that Syncthing's log was continiously saying that
accept: not implemented
. Missing dependencies or something?Reproduction steps
1. Install Syncthing 2. `tail -f .../@appstore/syncthing/var/syncthing.log` 3. ...
Install Log
Service Log
Other Logs
No response
The text was updated successfully, but these errors were encountered: