I’ve just bumped-up your user level, see if it works now.
No worries mate, I’m here to help. 
Your package version is quite-recent, so things are not looking too bad.
Let’s see if sherpa can fix this:
sherpa check
In the downtime before I saw your latest reply I entered sherpa update upgradable - and it’s running now… So when I do the sherpa check it should be the most recent
[Eric@QNAP451 ~]$ sudo sherpa upgrade upgradable
Password:
sherpa v251203-stable
done: actions complete.
• Package actions started @ 12:10:22 AM, ended @ 12:13:28 AM, elapsed = 3m:06s
• These package actions completed OK:
download ClamAV QPKG in 1 second
download duf QPKG in 1 second
download Bazarr QPKG in 1 second
download Glances QPKG in 1 second
download HideThatBanner QPKG in 1 second
download inxi QPKG in 1 second
download Kapowarr QPKG in 1 second
download Headphones QPKG in 1 second
download LazyLibrarian QPKG in 1 second
download Mylar3 QPKG in 1 second
download NZBHydra2 QPKG in 1 second
download nzbget QPKG in 1 second
download nzbToMedia QPKG in 1 second
download OliveTin QPKG in 1 second
download sha3sum QPKG in 1 second
download Par2turbo QPKG in 1 second
download pyLoad QPKG in 1 second
download TrguiNG QPKG in 1 second
download Unmanic QPKG in 1 second
download WebSSH QPKG in 1 second
deactivate SABnzbd QPKG in 1 second
deactivate pyLoad QPKG in 2 seconds
deactivate WebSSH QPKG in 2 seconds
deactivate LazyLibrarian QPKG in 3 seconds
deactivate Glances QPKG in 12 seconds
deactivate HideThatBanner QPKG in 1 second
deactivate Par2turbo QPKG in 1 second
upgrade duf QPKG in 5 seconds (v240731 -> v250927)
upgrade HideThatBanner QPKG in 10 seconds (v240807 -> v250927)
upgrade nzbget QPKG in 6 seconds (v24.5 -> v25.4)
upgrade OliveTin QPKG in 5 seconds (v241223 -> v251121)
upgrade Par2turbo QPKG in 11 seconds (v1.1.0 -> v1.2.0)
upgrade sha3sum QPKG in 5 seconds (v240808 -> v250706)
clean OliveTin QPKG in 1 second
reactivate Par2turbo QPKG in 1 second
reactivate Unrar QPKG in 1 second
reactivate Entware QPKG in 2 seconds
activate HideThatBanner QPKG in 1 second
upgrade TrguiNG QPKG in 5 seconds (v250123 -> v251121)
clean TrguiNG QPKG in 1 second
upgrade Bazarr QPKG in 6 seconds (v250123 -> v251121)
upgrade ClamAV QPKG in 5 seconds (v241223 -> v251121)
upgrade Glances QPKG in 11 seconds (v250123 -> v251121)
upgrade Headphones QPKG in 5 seconds (v250123 -> v251121)
upgrade inxi QPKG in 5 seconds (v240813 -> v251010)
upgrade Kapowarr QPKG in 5 seconds (v250123 -> v251121)
upgrade LazyLibrarian QPKG in 11 seconds (v250123 -> v251121)
upgrade Mylar3 QPKG in 5 seconds (v250123 -> v251121)
upgrade NZBHydra2 QPKG in 5 seconds (v241223 -> v251121)
upgrade nzbToMedia QPKG in 5 seconds (v240205 -> v251121)
upgrade pyLoad QPKG in 11 seconds (v250123 -> v251121)
upgrade Unmanic QPKG in 5 seconds (v250103 -> v251121)
upgrade WebSSH QPKG in 10 seconds (v250123 -> v251121)
clean Bazarr QPKG in 1 second
clean Glances QPKG in 1 second
clean Headphones QPKG in 1 second
clean Kapowarr QPKG in 1 second
clean LazyLibrarian QPKG in 1 second
clean Mylar3 QPKG in 1 second
clean NZBHydra2 QPKG in 1 second
clean nzbToMedia QPKG in 1 second
clean pyLoad QPKG in 1 second
clean Unmanic QPKG in 1 second
clean WebSSH QPKG in 1 second
• These package actions failed (and why):
activate Glances QPKG in 1 second (1)
activate SABnzbd QPKG in 1 second (1)
activate pyLoad QPKG in 1 second (1)
activate LazyLibrarian QPKG in 2 seconds (1)
activate WebSSH QPKG in 1 second (1)
[Eric@QNAP451 ~]$
sherpa check doesn’t upgrade anything. It performs a bunch of tests and tries to correct supporting packages if they’re missing. So, you’ll still need to run it. 
It’s running now… Will update as soon as it finishes.
1 Like
[Eric@QNAP451 ~]$ sudo sherpa check
Password:
sherpa v251203-stable
done: actions complete.
• Package actions started @ 12:16:24 AM, ended @ 12:18:48 AM, elapsed = 2m:24s
• These package actions completed OK:
install auxiliary PIP in 4 seconds
reactivate pyLoad QPKG in 30 seconds
reactivate Glances QPKG in 52 seconds
reactivate OSickGear QPKG in 9 seconds
reactivate SABnzbd QPKG in 37 seconds
reactivate WebSSH QPKG in 9 seconds
reactivate OTautulli QPKG in 16 seconds
reactivate LazyLibrarian QPKG in 49 seconds
• These package actions were skipped (and why):
"sign" duf QPKG in 1 second (already signed)
"sign" Entware QPKG in 1 second (already signed)
"sign" HideThatBanner QPKG in 1 second (already signed)
"sign" IncreaseTimeouts QPKG in 1 second (already signed)
"sign" nzbget QPKG in 1 second (already signed)
"sign" OliveTin QPKG in 1 second (already signed)
"sign" OReadarr QPKG in 1 second (already signed)
"sign" OSonarr QPKG in 1 second (already signed)
"sign" Par2turbo QPKG in 1 second (already signed)
"sign" QDK QPKG in 1 second (already signed)
"sign" sha3sum QPKG in 1 second (already signed)
"sign" sherpa QPKG in 1 second (already signed)
"sign" Unrar QPKG in 1 second (already signed)
"sign" TrguiNG QPKG in 1 second (already signed)
"sign" Bazarr QPKG in 1 second (already signed)
"sign" ClamAV QPKG in 1 second (already signed)
"sign" Glances QPKG in 1 second (already signed)
"sign" Headphones QPKG in 1 second (already signed)
"sign" inxi QPKG in 1 second (already signed)
"sign" Kapowarr QPKG in 1 second (already signed)
"sign" LazyLibrarian QPKG in 1 second (already signed)
"sign" Mylar3 QPKG in 1 second (already signed)
"sign" NZBHydra2 QPKG in 1 second (already signed)
"sign" nzbToMedia QPKG in 1 second (already signed)
"sign" OMedusa QPKG in 1 second (already signed)
"sign" OqBittorrent QPKG in 1 second (already signed)
"sign" OSickGear QPKG in 1 second (already signed)
"sign" OTautulli QPKG in 1 second (already signed)
"sign" OWatcher3 QPKG in 1 second (already signed)
"sign" pyLoad QPKG in 1 second (already signed)
"sign" SABnzbd QPKG in 1 second (already signed)
"sign" Unmanic QPKG in 1 second (already signed)
"sign" WebSSH QPKG in 1 second (already signed)
Looks good!
Now, clean SAB:
/etc/init.d/sabnzbd.sh clean
… and start it in debug mode this time:
/etc/init.d/sabnzbd.sh start debug
edit: Actually, looks like SAB was restarted during the check. Good. 
How’s its status look now?
/etc/init.d/sabnzbd.sh s
Also: don’t forget to migrate your ‘O’ packages: New QPKG names, and how-to start using them · OneCDOnly/sherpa · Discussion #321 · GitHub
[Eric@QNAP451 ~]$ sudo /etc/init.d/sabnzbd.sh clean
Password:
- source: sabnzbd.sh, action: clean, time: Thu 4 Dec 2025 12:26:18 AM CST, load: 0.17
- package: 251121, service: 251121, library: 251121
- QPKG enabled: false
- application auto-update: true
- active git branch: master
- daemon PID: none
> clean local repository: OK
> clean virtual Python environment: OK
> clean PyPI cache: OK
> remove application version: OK
> clean temp path: OK
= source: sabnzbd.sh, action: clean, time: Thu 4 Dec 2025 12:26:19 AM CST, result: OK, elapsed: 204ms, load: 0.17
[Eric@QNAP451 ~]$ sudo /etc/init.d/sabnzbd.sh start debug
- source: sabnzbd.sh, action: start, time: Thu 4 Dec 2025 12:26:41 AM CST, load: 0.12
- package: 251121, service: 251121, library: 251121
= 'SABnzbd' QPKG is disabled. Please enable it first with: /etc/init.d/sabnzbd.sh enable
= source: sabnzbd.sh, action: start, time: Thu 4 Dec 2025 12:26:41 AM CST, result: FAILED, elapsed: 16ms, load: 0.12
[Eric@QNAP451 ~]$
Will have to learn up on what migrating O packages means…
Don’t know why SAB is now disabled… that’s odd.
Please enable it again:
/etc/init.d/sabnzbd.sh enable
… and start it again:
/etc/init.d/sabnzbd.sh start debug
Wow - that debug list is long (and growing). Do you want to post it in its entirety?
Oooo - I just tried logging into the sabnzbd gui page and it came up!
I did the migration thing for sonarr - as it appears to be the only one that I’m using. Does that work for sabnzbd as well?
No, just keep an eye on it and look for the green line at the end (which means success). If you see a red line, we’ll need to investigate.
No, SABnzbd wasn’t an ‘O’ package, so nothing to migrate there.
Ok, then i think, once again, you’ve rewarded bad behavior and saved me… till next time. Much appreciated.
Incidentally - you asked about whether I was updating Sherpa… is there a way to have it do that automatically?
Looks like I hit the max number of replies in a given day… I am sooo green!
Not a clue what a cron is so no, not deliberately or knowingly. I have no problem going in to do it manually so long as I have a good, reliable CLI command.
No worries mate, cheers!
Typically, I’d suggest making it a cron job, but cron in QTS is a bit non-user-friendly. And it has a bad habit of removing user jobs.
Have you created cron jobs before?
Automatic updating can easily go-wrong. You’ve probably seen what happens when folks auto-update the firmware in their NAS. One-day, they can’t see it on the network anymore, because the update broke something.
Might be better to regularly run a manual update process instead? Maybe once per month?
Ugh… this forum sometimes… 
Yup, best one for you is:
sudo sherpa upgrade new
If you run this manually (it will usually finish in no-more than a few minutes), you can then take action if an upgrade goes south (breaks something).
If you generate a status report, you’ll get a notification if there are new packages available. No-need to run an upgrade unless there’s something to upgrade to! 
sudo sherpa status
@erkme73, this gives me an idea. I’ll consider including an automatic notifier that will put messages in the NAS system log if packages can be upgraded. It will run via a edit: even better: it will run as a daemon.cron job, and will install and maintain itself so you won’t need to know anything about cron.
With the right notification rules in QuLog, you can be notified of available upgrades via email: you won’t need to check for them.
Hey! I’m allowed to post again That’s sound like a wonderful plan. Just let me know if that’s something I have to initiate on my end, or will it just start popping up after I update to the version that has that change?
I’ve added the check/update CLI lines to a reminder to check more frequently either way.
Hi mate, nothing to-do at your end right now. It’ll take me a while to write and test this. It’s on my todo list, but there are a few other things I’m fixing right-now.
I’ll announce when it looks ready for testing.
1 Like
Hi OneCD,
You might remember me from a while back from the old forum, as the person with the really slow NAS (TS-119P II) which caused some problems (I might even be the person you have written IncreasedTimeOuts for). I have finally bought a new NAS. Because of your great help in the past, I got myself a TS-216G because I really like how Sherpa works and your fast continuous support.
Everything seems to work fine, so I just wanted to show my appreciation of the work you are doing! Keep up the good work!
1 Like