Unable to start NzbGet using NAS Diskstation DS413 running DSM 6.x

[ccwillia]

Is there already an issue for your problem?

• I have checked older issues, open and closed

NZBGet Version

v24.5-stable

Platform

NAS/Synology/QNAP

Environment

NAS Diskstation DS413 running DSM 6.x

Current Behavior

Upgraded from 24.1 to 24.5 which will not start. Logs mention lscpu not found and unable to determine cpu. I have tried to uninstall and reinstall but Nzbget will not run****

Expected Behavior

Nzbget would run after upgrade to 24.5

Steps To Reproduce

Use DSM community to install nzbGet
NzbGet never starts

Logs

Starting nzbget command /volume1/@appstore/nzbget/bin/nzbget -c /volume1/@appstore/nzbget/var/nzbget.conf -o WebDir=/volume1/@appstore/nzbget/bin/webui -o LockFile=/volume1/@appstore/nzbget/var/nzbget.pid -D
sh: lscpu: command not found
Thu Dec 12 22:43:38 2024 DETAIL Failed to get CPU model from '/proc/cpuinfo'
Thu Dec 12 22:43:38 2024 DETAIL Failed to get CPU model from 'lscpu'
Thu Dec 12 22:43:38 2024 INFO nzbget 24.5 daemon-mode
Thu Dec 12 22:43:38 2024 INFO using /volume1/@appstore/nzbget/var/nzbget.conf
Thu Dec 12 22:43:38 2024 INFO nzbget runs on 0.0.0.0:6789

Extra information

No response

[ccwillia]

Is it possible to move back to the 24.1 version until the issue is fixed? I wasn't able to find a noarch 24.1 version to install manually. Thanks in advance!

[dnzbk]

Yes, you can find and download previous versions here.

What’s the processor model in your Synology?

[ccwillia]

I tried some of the those versions. The Diskstation manual install only seems to accept SPK files which are only available under 24.1 and below. I don't see a noarch SPK file under 24.1 or one that matches my Diskstation architecture. Per this reference my DS413 has the Freescale P1022 CPU with package architecture Qoriq. I tried manually insalling this noarch SPK nzbget.v30.f15047[noarch].spk but it will not start similar to when i install through DSM Community directly. I assume that is version 24.5?

[phnzb]

@ccwillia Through the SynoCommunity package you can only install the latest testing / latest stable version, unfortunately downgrading is not supported.
The old version of SPKs doesn't support DSM6, so that's not possible either.
You have 2 options:

• install the old nzbget.net version via https://synocommunity.com/package/nzbget - version 20220406-29 (https://packages.synocommunity.com/nzbget/29/nzbget.v29.f7321%5Bnoarch%5D.spk).
• downgrade nzbget manually via ssh terminal:

1. Make sure SSH service is enabled (Control Panel - Terminal & SNMP - Enable SSH service)
2. Make sure User home service is enabled (Control Panel - User - Advanced - Enable user home service)
3. Install nzbget via Package Center (latest stable version)
4. Stop nzbget service via Package Center.
5. Find the link to the version of the linux installer you want to downgrade to (in example I will use 24.1 - https://github.com/nzbgetcom/nzbget/releases/download/v24.1/nzbget-24.1-bin-linux.run)
6. Login to NAS via SSH
7. Run from terminal (use link from p.5, for sudo prompt use yours user password):

curl -LO https://github.com/nzbgetcom/nzbget/releases/download/v24.1/nzbget-24.1-bin-linux.run
sh nzbget-24.1-bin-linux.run
sudo cp nzbget/nzbget /volume1/@appstore/nzbget/bin/nzbget
sudo cp nzbget/7za /volume1/@appstore/nzbget/bin/7za
sudo cp nzbget/unrar /volume1/@appstore/nzbget/bin/unrar
sudo cp -r nzbget/webui /volume1/@appstore/nzbget/bin
sudo chown sc-nzbget:sc-download /volume1/@appstore/nzbget/bin/*
rm -rf ./nzbget
rm nzbget-24.1-bin-linux.run

9. Start nzbget via Package Center and do not upgrade it via internal updater

[ccwillia]

I am able to install and run the old nzbget.net version 21.1. I will try updating again through DSM then run the steps you provided below to move back to 24.1 which was working prior to clicking the internal updater. Hopefully this issue in 24.5 or future release can be fixed so i can keep current with the releases

[ccwillia]

Thanks for the steps above i was able to move back to 24.1 which runs successfully. Let me know if any additional information is need to address the bug or if there is a future fix you would like me to test