-
-
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] fails to start after system update to DSM 6.1.4-15217 Update 5 #3058
Comments
Having same exact issue with NZBGET |
Ok, so who could help with this? I'm really depending on my data sync setup... I'd fix it myself if I had any experience with synology packaging, but I've just owned the box for a couple of weeks now. It should be something pretty simple that prevents syncthing from running... and reading from @SirAce135 's comment, Synology seems to have put out an update that messes with more than just one package. Is no one else concerned? Can I provide anything else that would facilitate the troubleshooting? |
Same problem here (but already with DSM version
reinstalling the package solves the problem. (settings are gone, make a backup beforehand) |
Reinstalling fixed it for me as well. Could this issue be prevented though? |
For new Package Requests, see the guidelines
Setup
Package Name: Syncthing
Package Version: 0.14.30-13
NAS Model: DS1517+
NAS Architecture: ?
DSM version: DSM 6.1.4-15217 Update 5
Expected behavior
I've been running Syncthing 0.14.30-13 flawlessly for the last couple days, with no manual intervention. I was on DSM 6.1.4 Update 3.
Actual behavior
After upgrading to DSM 6.1.4-15217 Update 5, the service won't start and fails a generic "Failed to run the package service" error in Package Center when I run it manually
Steps to reproduce
1. update to DSM 6.1.4-15217 Update 5
2. (Syncthing not starting)
3. Attempt to start Syncthing in Package Center
Package log
Check Package Center or
/usr/local/{package}/var/
There are no logs on this except the (irrelevant):
Other logs
E.g.
/var/log/messages
or/var/log/synopkg.log
The text was updated successfully, but these errors were encountered: