[QPKG] sherpa: a mini-package-manager (CLI)

Cheers mate! :slight_smile:

No, but I sincerely appreciate your kind offer. Thank you. :+1:

Just saw this and have a question:

Does this mean that if I start up sherpa, it will update Entware and Watcher3 will then not be functional anymore?

@FoP, correct (unfortunately).

Well, nothing lasts forever, and Watcher3 had a good run on my old TS-439 Pro II+ :slight_smile:

Got everything else upgraded and now I want to remove whatever is left of Watcher3, but I’m honestly not sure if removing the QPKG in the UI is enough or if I should should fire up WinSCP and delete something through that. Any recommendations for removing any trace of Watcher3?

Yup, removing the QPKG via the App Center is enough to remove all traces of it - unless you put the database in a custom location. :wink:

Hi OneCD,

Ive been having massive issues with my sherpa install after restarting my NAS. I shutdown my NAS this morning because there was going to be a scheduled power outage. Upon restarting, everything started up (Sonarr, qBittorrent etc) except for SABnzbd. Looking at the debug logs it came with the following error “module ‘sabctools’ has no attribute ‘NNTPResponse’” . I tried to restart/reinstall sab via sherpa but still the error persisted. I also did a check on dependencies etc. I thought sherpa was busted so i issued the sherpa clean command. Ive uninstalled and reinstalled the current version and older versions of sherpa and they are all failing with the error “/share/CACHEDEV1_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: No such file or directory” . Ive also reinstalled Entware to no avail. Im kinda stuck now as my sab is not working and I cant even fix it with sherpa because that is busted too. Any help would be greatly appreciated.

EDIT: It seems like Ive had the same issue as one of the users above. It seems like ive broken a lot of things trying to do a PIP repair earlier as well as now sabnzbd states a different error related to missing python3 (even though its installed).

Hi @Vtaggar and welcome to the forum. :slight_smile:

Let’s get sherpa working first.

Please reinstall it with:

curl -skL https://tinyurl.com/get-sherpa > /share/Public/sherpa.qpkg;
sudo sh /share/Public/sherpa.qpkg;

… then run a fix operation:

sudo sherpa fix

Let me know if you see any errors.

Yep i tried that. It gives me the sherpa manager error mentioned above. It was working initially but then stopped after I ran the clean command and it removed the cache.

This does sound like the same issue reported by an earlier user. Unfortunately, they haven’t responded further, so I haven’t been able to find-out what went wrong. :frowning:

Try this please (these are not fixes, just diagnosis tools):

/sbin/curl 'https://raw.githubusercontent.com/OneCDOnly/sherpa/stable/sherpa-manager.tar.gz' > /share/Public/temp.tar.gz;
ll /share/Public/temp*

If Entware is installed, you should also have access to GNU file, so let’s use it:

file /share/Public/temp.tar.gz

Please post back what you see.

/sbin/curl ‘https://raw.githubusercontent.com/OneCDOnly/sherpa/stable/sherpa-manager.tar.gz’ > /share/Public/temp.tar.gz;
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: curl - SSL CA Certificates

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

The other command said command not found even though Ive installed entware

What is your firmware version please? And NAS model?

Try that curl command again but this time, don’t verify the SSL certificate. Include the -k curl argument to do this.

I might have to update my firmware as its quite old (2021). I suspect the QNAP (TS451) is blocking installs or doing something funky. Let me update and get back to you.

EDIT: So issuing that command with -k worked. I cant execute it due to entware issue

EDIT2: I managed to extract the archive and move the sherpa-manager file into the correct spot. Sherpa is back!

EDIT3: Spoke too soon

 sherpa fix
warn: Remote file download failed
sherpa v260505-stable
bort: no 'objects' archive exists to extract from, can't continue.

Yup, sherpa will auto-download it again on its own and some other files too. It will keep trying without the -k option based-on your installed QTS firmware version.

Which QTS version is presently installed please?

Busy-now, but I’ll check back later. :slight_smile:

Thanks. Ive updated to the latest firmware 5.2.9.3451 and it seems to be progressing now. I think my FW was too old for stuff to run. Ill let you know how i go when I try to run sab

EDIT: So sab still refuses to start due to sabctools requirement

It must have been old, SSL certificate verification only started working partway through the QTS 4.5.4 release period. :wink:

Run a fix please:

sherpa fix

then clean your SABnzbd QPKG:

sherpa clean sab

If SABnzbd wasn’t started after the clean, please start it with:

sherpa start sab

Mixed results again. I ran the commands and it failed with the following:

[/share/CACHEDEV1_DATA/.qpkg/SABnzbd] # sherpa start sab
sherpa v260505-stable
note: new QPKG versions are available for Entware, Par2turbo & 1 other.
done: actions complete.

• Package actions started @ 2:20:29 PM, ended @ 2:20:42 PM, elapsed = 13 seconds

• These package actions completed OK:
    reactivate Par2turbo QPKG in < 1 second
    reactivate Unrar QPKG in < 1 second
    reactivate Entware QPKG in 1 second

• This package action failed (and why):
    activate SABnzbd QPKG in 5 seconds (not-found)

Trying to start it manually allowed it to progress past the previous hurdle (sabctools) but then failed to start

 File "/share/CACHEDEV1_DATA/.qpkg/SABnzbd/repo-cache/sabnzbd/misc.py", line 40, in <module>
    import rarfile
ModuleNotFoundError: No module named 'rarfile'
} exec: completed, but with errors
= start daemon: failed
= source: sabnzbd.sh, action: start, time: Wed 13 May 2026 2:19:46 PM EST, result: FAILED, elapsed: 0h:01m:23s, load: 3.30

There’s a message there indicating new QPKGs are available. Can you please upgrade your QPKGs too?

sherpa upgrade new

Thank you! That has finally worked. Appreciate your work in creating sherpa and your help!

No worries mate.

It helps a great deal if you keep your software up-to-date. :wink: