Skip to content
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 4.0.3-64 core dumped at startup on qoriq #5847

Closed
1 task done
zaadstra opened this issue Aug 15, 2023 · 85 comments · Fixed by #5866 or #5879
Closed
1 task done

sabnzbd 4.0.3-64 core dumped at startup on qoriq #5847

zaadstra opened this issue Aug 15, 2023 · 85 comments · Fixed by #5866 or #5879
Assignees
Labels
bug build/rust-qoriq related to rust target powerpc-unknown-linux-gnuspe (instead of powerpc-unknown-linux-gnu)

Comments

@zaadstra
Copy link

Is this a new Bug?

  • I checked that the bug hasn't been reported before

Package Name

sabnzbd

Package Version

sabnzbd 4.0.3-64

Device Model

DS213+ Qoriq

Device Architecture

PPC

Firmware Version

6.2.4 latest

What happened?

Update sabnzbd 4.0.3-63 to sabnzbd 4.0.3-64. Then got an error "cannot start package service".

Some analysis has been done in issue 5841. Issue seemed related at first but it is different. First thougts by @th0ma7

Your pip calls are working out just fine, meaning you do have openssl working ok. The issue in your case really is the core dumped which I presume is due to cryptography wheel. I'll have to investigate a bit further.

I uploaded the logs to pastebin, both for Python 3.11 and sabnzbd.

python311.log ds213+ https://pastebin.com/Lw5NGb1S

sabnzbd.log ds213+ https://pastebin.com/uCqQFh04

2023/07/22 00:01:44 sabnzbd 4.0.2-62 -> 63
2023/08/14 13:25:52 sabnzbd 4.0.3-63 -> 64

(fails to start)
2023/08/14 13:35:38 start sabnzbd 4.0.3-64 Begin start-stop-status start
/var/packages/sabnzbd/scripts/start-stop-status: line 31: 15558 Illegal instruction (core dumped) ${service} >> ${OUT} 2>&1
2023/08/14 13:36:05 start sabnzbd 4.0.3-64 End start-stop-status start ret=[1]
2023/08/14 13:36:06 (system) trigger sabnzbd 4.0.3-64 Begin start-stop-status stop
2023/08/14 13:36:06 (system) trigger sabnzbd 4.0.3-64 End start-stop-status stop ret=[0]

(reboot)

2023/08/14 13:55:26 start sabnzbd 4.0.3-64 Begin start-stop-status start
/var/packages/sabnzbd/scripts/start-stop-status: line 31: 12265 Illegal instruction (core dumped) ${service} >> ${OUT} 2>&1
2023/08/14 13:55:56 start sabnzbd 4.0.3-64 End start-stop-status start ret=[1]
2023/08/14 13:55:57 (system) trigger sabnzbd 4.0.3-64 Begin start-stop-status stop
2023/08/14 13:55:57 (system) trigger sabnzbd 4.0.3-64 End start-stop-status stop ret=[0]

(uninstall)
2023/08/14 13:56:29 uninstall sabnzbd 4.0.3-64 Begin preuninst

(reinstall v64 from package service)
2023/08/14 13:57:46 install sabnzbd 4.0.3-64 Begin preinst

(uninstall)
2023/08/14 14:01:04 uninstall sabnzbd 4.0.3-64 End postuninst ret=[0]

(install v63 from .spk)
2023/08/14 14:02:33 install sabnzbd 4.0.3-63 Begin preinst

Reproduction steps

  1. updated via package system, error
  2. uninstalled and reinstalled via package system, error
  3. uninstalled and installed previous version .spk, working

... see steps above pointing to log details

Install Log

python311.log ds213+ https://pastebin.com/Lw5NGb1S

sabnzbd.log ds213+ https://pastebin.com/uCqQFh04

Service Log

No response

Other Logs

No response

@zaadstra zaadstra added the bug label Aug 15, 2023
@zaadstra zaadstra changed the title sabnzbd -64 core dumped at startup on qoriq sabnzbd 4.0.3-64 core dumped at startup on qoriq Aug 15, 2023
@ppaaull
Copy link

ppaaull commented Sep 3, 2023

Hi,
Yesterday I did 3 updates (Python 3.10, Python 3.11 and Sabnzb 4.0.3-64)
After the updates Sabnzb doesn't start anymore. If shows the message "cannot start package service" (In dutch "Kon de pakket service niet uitvoeren").
Seems the same issue as described above.
Is there any update on this bug or is there a work-arround available ?!

@zaadstra
Copy link
Author

zaadstra commented Sep 3, 2023

Hi @ppaaull ,

Which model are you running?

From this page I grabbed the previous version of the package and installed manually. For my DS213+ that is sabnzbd.v63.f25556[qoriq].spk.

Because before this apk install, I uninstalled and reinstalled via Syno package management, I lost my settings. If you have a recent settings export you can just re-import this and continue with v63. If not, you may try to install tha apk over the current installed v64 package, Ido not know if this is possible however.

My lesson learned: create a settings backup once in a while. Might be a nice feature for Sab to do this automagically ;-)

@mreid-tt
Copy link
Contributor

mreid-tt commented Sep 3, 2023

There is an option in the FAQ to Downgrade a package without uninstalling (Advanced) which you can use to possibly avoid uninstalling SABnzbd.

@th0ma7 th0ma7 linked a pull request Sep 3, 2023 that will close this issue
10 tasks
@zaadstra
Copy link
Author

zaadstra commented Sep 3, 2023

Reading the conclusions in #5820 (comment), what are now the supposed steps for Qoriq? Is Qoriq actually ARMv5? I read of "Freescale's e500 Power Architecture technology".

Python v3.11.4-7 and SABnzbd v4.0.3-63 seem to work correctly now on DS213+/Qoriq, but the Syno continues mentioning there is an update and it continues moaning that "Packages on nas8001 are out-of-date".

The current Python 3.11 and the new SABnzbd v64 are still available on the SC webpages.

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 4, 2023

@zaadstra qoriq is a ppc type architecture (e.g. not armv5). I am unsure wetter I'll be able to solve your issue or not. But my hope is that fixes part of #5866 will do the trick.

On that matter, could you test out packages from the automated github-action builds? The last build is here: https://github.com/SynoCommunity/spksrc/actions/runs/6066594750

Look for a zip file for your qoriq architecture. In the zip file you'll find a python311 package update (to install first) then an updated sabnzbd package. Let me know how things turns out, and provide installation logs (from /var/log/packages/ directory).

@ppaaull
Copy link

ppaaull commented Sep 4, 2023

Thanks for your comments.

In addition to my post from yesterday ..
I have a NAS DS213+.

Unfortunately I am not familiar with installing apps manually.
So I hope someone can help me and or guide me with fixing from DSM 6

Thanks in advance

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 4, 2023

@ppaaull here's a quick howto:

  1. download the package file onto your desktop
  2. from there unzip the package file to extract all the .spk
  3. from your Synology NAS in the package center you can select "Manual install"
  4. from there you can select the .spk from your desktop
  5. start with python311 followed by sabnzbd

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 4, 2023

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 8, 2023

Similar issue as #5684

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 10, 2023

@zaadstra have you tried installing github-action generated files to confirm it works out?

Also, you are referring to a core dump but I can't find it anywhere? Usually they are being copied over under your /volume1 directory, called something like @sabnzbd.synology_apollolake_918+.42962.core.gz

@zaadstra
Copy link
Author

Well, I looked at the github page and saw too many options. I was not very keen on breaking my """production""" system again, and being in a situation not knowing how to unmess the experimental stuff. The older sab is working with the newer Python now (3.11.4-7).

Meanwhile the ds213+ offered a sabnzbd update ("out of date") which magically disappeared after a while. I notice that the package for Qoriq disappeared and now 4.0.3-65 also doesn't support qoric.

Now ds213+ reports an update for Python (3.11.4-7 to 3.11.5-8) but I'm not sure if that will break things too.

I found the dump dated 14/8 which I will attach here. (8.94 MB)
python3.core.gz

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 14, 2023

@zaadstra and @ppaaull we may have found where the issue is (fingers crossed).

We have a set of debug-enabled packages available here (look down under the artifact section on the right): https://github.com/SynoCommunity/spksrc/actions/runs/6188300522?pr=5879

Would you mind installing them manually using your package center top-right manual install option. You only require to install first python 3.11 package then the sabnzbd package. Note that you first have to decompress the .zip file that contains the actual packages (.spk).

Please report your results (success or failure). In case of failure we'll provide you with additional instructions to install debugging tools part of the synocli-devel package to "backtrace" events and find where the issue may be (synocli-devel package is also included in the .zip file, but not need to install it for the moment).

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 17, 2023

@zaadstra
Copy link
Author

Hi, I'm out of town but will test when back.

To recap:

  • do I need to uninstall python and sab first?
  • I should expect that things get broken and look for error logs?

@ppaaull
Copy link

ppaaull commented Sep 18, 2023

Hi All,

I finally find the time to look at this and try some of the above suggestions.

The first option I tried is to remove the (not working) installation (I thought version 4.0.3-64) from my DS213+
Next I installed Sabnzb again from the community package-center. That was installing version 4.0.3-63
And it worked 😏
So for now I'm up and running again.

On https://synocommunity.com/package/sabnzbd I see the latest version is 4.0.3-65.
But I'll wait untill Synology suggest an update

Thanks for all the help and suggestions the last few weeks

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 18, 2023

@zaadstra

  • do I need to uninstall python and sab first?

normally no.

  • I should expect that things get broken and look for error logs?

my hope are that this will either

  1. fix things OR
  2. allow debugging things (as package have low-level compile-time debug_info symbols included).

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 18, 2023

@ppaaull

The first option I tried is to remove the (not working) installation (I thought version 4.0.3-64) from my DS213+ Next I installed Sabnzb again from the community package-center. That was installing version 4.0.3-63 And it worked 😏 So for now I'm up and running again.

I'm glad you got it working again.

On https://synocommunity.com/package/sabnzbd I see the latest version is 4.0.3-65. But I'll wait untill Synology suggest an update

This will not hapen: the packages are provided by SynoCommunity, not Synology.

I need your help so we (synocommunity project aka github spksrc) find a suitable solution to the issue. Updating both python311 and sabznbd to https://github.com/SynoCommunity/spksrc/actions/runs/6216557950 along with providing logs will hopefully provide sufficient traces to locate where the issue exactly is.

@zaadstra
Copy link
Author

@th0ma7

Remember it works now, 4.0.3 [9fafe64] with latest Python (for Qoriq).

So only manually installing the SABnzbd package would provide enough info? It is a working system (now), it is used often and I am trying to break as less as possible ....

@th0ma7
Copy link
Contributor

th0ma7 commented Sep 18, 2023

@zaadstra hold-on, I may have find where the issue is. I'll be publishing an updated URL for updated packages.

@zaadstra
Copy link
Author

zaadstra commented Dec 4, 2023

Voila:
@python3.core.gz
7.26 MB

@marcofranssen
Copy link

See #5684 (comment) on the last stuff I tested. Let me know if I should test something else or new changes.

@zaadstra
Copy link
Author

zaadstra commented Jan 12, 2024

A new 4.2.1-67 is offered to DS213+ DSM 6.2.4 Qoriq boxes. It installs but fails to run ....

@th0ma7
Copy link
Contributor

th0ma7 commented Jan 12, 2024

Yeah, issue isn't fixed yet. I'm getting closer to a solution (fingers crossed) but ain't there yet.

@zaadstra
Copy link
Author

Alright current version works fine, so no rush. But now a new version is offered on Synocommunity, DSM starts moaning that I have an old package installed (since when did this start...). Better remove the broken package then from the SC website.

@mreid-tt
Copy link
Contributor

mreid-tt commented Jan 21, 2024

I've removed the 6.2 qoriq build from SABnzbd v4.2.1-67. @Safihre do take note of this; we need to manually remove such builds until this issue is resolved.

@Safihre
Copy link
Contributor

Safihre commented Jan 21, 2024

@mreid-tt Thanks! Really forgot about this..

@zaadstra
Copy link
Author

zaadstra commented Jan 22, 2024

This is weird, it still keeps moaning. (=offering the update ;-) )
I even removed the SC package source, and then added it again. And there's the update again as well.
At the previous withdrawal from the SC site, the update did automagically disappear.
@Safihre @mreid-tt

@mreid-tt
Copy link
Contributor

@zaadstra, if you take a look at https://synocommunity.com/package/sabnzbd, you will note that the last version which includes a qoriq build for DSM 6.x is v4.0.2-62. Is it that you are seeing a newer version? If so, it's possible that the DSM has not updated its cache of the catalog of available updates. This can take one to two days to refresh. Alternately, if the refresh button is not performing a catalog update you can try restarting your NAS which should cause a refresh.

@zaadstra
Copy link
Author

@mreid-tt It is in the DSM Package Center:
image

I was trying to force refreshing any cache or lists bij deleting SC as package source, but no luck. Yes, when SC as source was gone, the update was gone as well. But as soon SC was added as source, the update showed up as well. I'll give it some days, and otherwise reboot.

@hgy59
Copy link
Contributor

hgy59 commented Jan 22, 2024

I was trying to force refreshing any cache or lists bij deleting SC as package source, but no luck.

Is is not your local cache, but the CDN of synocommunity repository. It takes up to 48h until newly published packages are visible on the clients. The same delay seems to act on package removal...

@zaadstra
Copy link
Author

Thanks for explaining.

@th0ma7
Copy link
Contributor

th0ma7 commented Jan 25, 2024

@zaadstra and @marcofranssen new package for testing available at https://github.com/SynoCommunity/spksrc/actions/runs/7658491362

@th0ma7
Copy link
Contributor

th0ma7 commented Jan 28, 2024

Any chances someone can test it out? As this has a lot of importance for continuing to support this CPU architecture for many other software we publishes. Much thnx in advance.

@zaadstra
Copy link
Author

zaadstra commented Jan 28, 2024

@th0ma7
image

I guess we can call that a success!!! I only got a "package does not contain digital signature" message.

... and just tested a .nzb and it actually works too :-)

Congrats to win the battle and thanks for all the efforts 👍

@th0ma7 th0ma7 linked a pull request Jan 28, 2024 that will close this issue
10 tasks
@th0ma7
Copy link
Contributor

th0ma7 commented Jan 28, 2024

This is awesome, thnx for testing and what a journey this was.

@zaadstra In order to have this one fully closed, would you mind testing the latest build: https://github.com/SynoCommunity/spksrc/actions/runs/7681251146
Some changes where made to reduce build time but I'd need to confirm that it didn't had any impact on the end-result.

@zaadstra
Copy link
Author

zaadstra commented Jan 28, 2024

Yup, from the package manager:

image

Still going strong 👍 Just installed over the previous version, did not uninstall/reinstall.

@th0ma7
Copy link
Contributor

th0ma7 commented Jan 28, 2024

@zaadstra thnx for testing it out!

@Safihre
Copy link
Contributor

Safihre commented Feb 5, 2024

I removed qoriq for the 4.2.2 update. No others needed to be removed, right?

@th0ma7
Copy link
Contributor

th0ma7 commented Feb 5, 2024

Nope, just qoriq. And i am about to merge the fix for that soit qoriq becomes functional again

@th0ma7
Copy link
Contributor

th0ma7 commented Feb 5, 2024

Updated packages to follow normal flow part of next package upgrades to come. Feel free to re-open if issue comes up again but I believe its now fully addressed. Thnx for your time at testing, cheers.

@mreid-tt
Copy link
Contributor

mreid-tt commented Feb 6, 2024

@th0ma7, @Safihre, I can re-publish the current version of sabnzbd 4.2.2 using the new code for qoriq if you'd like.

@Safihre
Copy link
Contributor

Safihre commented Feb 6, 2024

Sounds good!

@th0ma7
Copy link
Contributor

th0ma7 commented Feb 6, 2024

Is a python311 also still available?

@mreid-tt
Copy link
Contributor

mreid-tt commented Feb 6, 2024

Sounds good!

The qoriq version has been published. @zaadstra feel free to test when it becomes available in the package center in a day or two or you can manually download from https://synocommunity.com/package/sabnzbd.

Is a python311 also still available?

As far as I know https://synocommunity.com/package/python311 has a Python v3.11.5-8 for qoriq. Are you suggesting that it be re-published?

@th0ma7
Copy link
Contributor

th0ma7 commented Feb 6, 2024

We should be good then, no need to republish

@zaadstra
Copy link
Author

zaadstra commented Feb 6, 2024

The qoriq version has been published. @zaadstra feel free to test when it becomes available in the package center in a day or two or you can manually download from https://synocommunity.com/package/sabnzbd.

Will do!

Is a python311 also still available?

As far as I know https://synocommunity.com/package/python311 has a Python v3.11.5-8 for qoriq. Are you suggesting that it be re-published?

Correct, I have 3.11.5-8 running. Not sure if this was repo or a testing package tho ...

@zaadstra
Copy link
Author

zaadstra commented Feb 7, 2024

@mreid-tt The DS213+ sent a notify for an updated package, the SABnzbd 4.2.2-68 was ready for update.
Updating went flawless and the package is running. And it's still working and downloading ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug build/rust-qoriq related to rust target powerpc-unknown-linux-gnuspe (instead of powerpc-unknown-linux-gnu)
Projects
None yet
7 participants