-
-
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
sabnzbd not starting after upgrade sabnzbd to version 4.0.2-62 and Python to version 3.11.4-6 on my NAS DS212+ #5841
Comments
I forgot to upload the service log:
|
Nope not related. This looks like the user as network issues somehow or that he is unable to resolve destination ssl certificate. I would suggest uninstalling the reinstalling. If he does not want to loose his configs he could the manually download the package from our server then install manually over the existing. |
Are you sure of this? Look at this section of the log:
Wouldn't this suggest something missing in Python rather than a network issue? Should he uninstall and re-install Python 3.11? |
Good catch, indeed this looks new to me. Indeed providing python logs may help. Along with reinstalling python311. But something's fishy... |
Hi all, |
The Python installation log seems to say about the same thing:
It may be that Python needs to be completely uninstalled and re-installed. @th0ma7 what do you think? |
Maybie... Or that there is a new pip version which introduces a new behavior. I'll have to try to reproduce on my end and maybe enforce using a fixed pip version instead . |
I have the same problem, also with Python 3.11.4-7 version of today. I cannot see any loggings, just that the sabnzbd cannot start. Also on NAS 212 |
@th0ma7 We are getting multiple reports of this. EDIT: To clarify, the |
@th0ma7 Just to help set some context for this, I can confirm that on my DS916+ (Braswell arch, x64) with SABnzbd v4.0.3-64 and Python 3.11 v3.11.4-7 it works perfectly fine with the latest DSM 7. It could be a DSM 6 issue as suggested or perhaps an ARMv5 arch issue. |
Same issue here, DS213+ (Qoriq) with DSM 6.2.4. Strange thing that I got this version upgrading from SAB v63 to v64. Yesterday that gave an error about not updating because of Python 311 (this was on board). Today a new Python 311 package was offered, installed it and then SABnzbd v64, which succeeded. Then got an error "cannot start package service". Uninstalled v64, reinstalled, no luck. Then grabbed the v63 .spk and this works. By the way I see a huge size difference between the v63 and v64 spk's. Another note: I also run a DS218+, same Python 311 update and then SAB v64 update. Running fine. |
@zaadstra could you get the logging through ssh? See if you get the same error. |
@zaadstra This was expected as it now relies on python311 libraries instead of re-providing it's own.
Can you be more specific? the update works well on your DS218+ ( Also, are you hitting the same issue as @MartinWingelaar where you have the following in your installation logs (
|
@th0ma7 actually the new package (6.2MB) is bigger than the old (4.7MB) not smaller. |
Both DS213+ and DS218+ are running DSM 6.2.4 latest update.
Correct.
Correct. For Qoriq v63 is 4610 KB and v64 is 6060 KB. I uploaded the logs to pastebin, both for Python 3.11 and sabnzbd, for both NAS models: python311.log ds218+ https://pastebin.com/WKFYnHv7 python311.log ds213+ https://pastebin.com/Lw5NGb1S sabnzbd.log ds218+ https://pastebin.com/RhVYZm5N 2023/07/27 13:43:36 upgrade sabnzbd 4.0.2-62 -> 63 sabnzbd.log ds213+ https://pastebin.com/uCqQFh04 2023/07/22 00:01:44 sabnzbd 4.0.2-62 -> 63 (fails to start) (reboot) 2023/08/14 13:55:26 start sabnzbd 4.0.3-64 Begin start-stop-status start (uninstall) (reinstall v64 from package service) (uninstall) (install v63 from .spk) Hope this helps. |
@zaadstra this confirms my theory whereas your problem is different than the one encountered by @MartinWingelaar. Your Can you please open-up a different issue relatively to |
Done, core dump goes to issue 5847. |
@MartinWingelaar Just returned from vacation and was able to find some time to further investigate. It hapens that ARMv5 can no longer be supported and a python 3.11 package update should not have been made available to your platform. The workaround for you is to revert to a previous version of Python 3.11 being version 3.11.4-6 (manually available at https://synocommunity.com/package/python311). To manually downgrade you can follow this guide https://github.com/SynoCommunity/spksrc/wiki/Frequently-Asked-Questions#downgrade-a-package-without-uninstalling-advanced or simply uninstall and re-install the proper version (but will lose your local preferences). In the meantime, I've removed the culprit package from our repository online to avoid other similar issues. More information available at #5820 (comment) |
@th0ma7, this version of Python v3.11.4-6 does not seem to be available online anymore. Having a similar issue reported by an ARMv5 user but using EDIT: Refer to #5990 for details. |
Is this a new Bug?
Package Name
sabnzbd
Package Version
4.0.2-62
Device Model
DS212+
Device Architecture
ARMv5
Firmware Version
6.2.4-25556 Update 7
What happened?
After I installed the latest version of Sabnzbd 4.0.2-62 and Python 3.11.4-6 on my Synology NAS DS212+ sabnzbd is not starting.
My NAS is running DSM 6.2.4-25556 Update 7
The message in the log says:
Reproduction steps
Install Log
https://pastebin.com/cqLesaL7
Service Log
No response
Other Logs
No response
The text was updated successfully, but these errors were encountered: