Hi Martin. 
Sorry, GitHub is having a meltdown right now… lots of issues. We’ll need to wait for it to be resolved by the MS folks.
Maybe it’s time to jump ship to GitLab? ¯\_(ツ)_/¯
Please make sure to post in English
Sorry, I forgot again. Thanks for your translation.
Hi OneCD!
Oh dear, all that fuss for nothing again…
Well, I’ll just wait until GitHub is working again and reinstall everything… 
Thank you.
You may not need to resort to QPKG uninstall/reinstalls to fix problems. It depends on the issue. Most of the previous issues requiring QPKGs to be reinstalled have been resolved.
If you have an issue, try a sherpa fix first. If that doesn’t fix it, check the service script logs for that specific QPKG and look for errors. If no luck there, please contact me, I’m always happy to assist. 
I’ve already uninstalled sab. When I try to reinstall it, I get the error message:
"warn: Remote file download failed"
This error message also appears when using sherpa fix. I’ll just wait until GitHub is working again. If it still won’t install after that, I’ll gladly take you up on your offer. 
Yup, we’ll need to wait for GitHub to start working again before you can continue.
Thanks. Sab is working again. 
Thanks OneCD for your prompt reply. Would there be any way to add an updated version to your repository?
Regards
If you can find newer Transmission binaries (from a reputable source) able to run inside QTS, I’m happy to make them available through sherpa.
If your NAS model supports containers, you could run a docker image of the latest Transmission.
Update
FileBrowser users: the devs recently discontinued development of FileBrowser and archived their repository on GitHub.
FileBrowser will continue to be available as an installable sherpa QPKG, but won’t be updated any further. This means auto-update can be disabled for this QPKG.
I’m currently looking at creating a new QPKG for one of the FileBrowser forks called FileBrowser Quantum.
Are there any current users of FileBrowser Quantum on here?
Wanted to update SABNzbd and Sickgear, and logging into my TS-439 Pro II+ and doing a sherpa status I get these errors before it then ends up showing the status for the services installed
[~] # sherpa status
proc: init ... /share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
sherpa v260908-stable (i86)
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
proc: refresh QPKG states ... /share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
and it continues for quite a bit.
That doesn’t seem right
Oops. 
Can you please post the output from this command?
head -n8 /etc/config/uLinux.conf
Edit: also, can you try generating an about report? It will show errors too, but should mostly be OK:
sherpa about
Both commands here
[~] # head -n8 /etc/config/uLinux.conf
[System]
Model = TS-439PROII+
Internal Model = TS-459
Server comment = NAS Server
Version = 4.2.6
Build Number = 20240618
Time Zone = Europe/Paris
Enable Daylight Saving Time = TRUE
[~] # sherpa about
proc: init ... /share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
proc: objects ... /share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
proc: database ... /share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
sherpa v260908-stable (i86)
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
dbug: (II) ---------------------------------------------------------------------------------------------------------
dbug: (**) HARDWARE: NAS model: TS-439 Pro II+
dbug: (**) HARDWARE: CPU: Intel(R) Atom(TM) CPU D425 @ 1.80GHz
dbug: (**) HARDWARE: CPU stepping: 10
dbug: (**) HARDWARE: available CPU threads: 2
dbug: (**) HARDWARE: CPU architecture: x86_64 (64b)
dbug: (**) HARDWARE: basic CPU SHA1 benchmark: 39.6MB/s
dbug: (**) HARDWARE: RAM: 0.96GiB
dbug: (**) KERNEL: name: Linux
dbug: (**) KERNEL: version: 3.4.6
dbug: (**) KERNEL: page size: 4kiB
dbug: (**) FIRMWARE: OS: QTS
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
dbug: (WW) FIRMWARE: version: 4.2.6.undefined
dbug: (**) FIRMWARE: build date: 20240618 (Tue 18 Jun 2024)
dbug: (**) FIRMWARE: platform: X86_PINEVIEW
dbug: (**) OS: state: online
dbug: (**) OS: uptime: 9106h:13m:43s
dbug: (**) OS: load averages: 0.19 (1m), 0.07 (5m), 0.05 (15m)
dbug: (**) STORAGE: default volume mounted: /share/MD0_DATA
dbug: (**) STORAGE: basic write benchmark: 136MB/s
dbug: (**) STORAGE: /opt: /share/MD0_DATA/.qpkg/Entware
dbug: (**) USERSPACE: libc: (GNU libc) 2.6.1
dbug: (**) USERSPACE: libc copyright: Copyright (C) 2007 Free Software Foundation, Inc.
dbug: (**) USERSPACE: $EUID: 0
dbug: (NA) USERSPACE: $SUDO_UID: N/A
dbug: (**) USERSPACE: BusyBox version: BusyBox v1.01 (2024.06.17-18:26+0000) multi-call binary
dbug: (**) USERSPACE: BusyBox function count: 133
dbug: (**) SCRIPT: QPKG version: 260901 (Tue 1 Sep 2026)
dbug: (**) SCRIPT: manager version: v260908-stable (i86)
dbug: (**) SCRIPT: manager epoch: 1788826450 (Tue 8 Sep 2026 2:14:10 AM CEST)
dbug: (**) SCRIPT: objects epoch: 1788826446 (Tue 8 Sep 2026 2:14:06 AM CEST)
dbug: (**) SCRIPT: packages epoch: 1788642957 (Sat 5 Sep 2026 11:15:57 PM CEST)
dbug: (**) QPKG: package release: v260906 (Sun 6 Sep 2026)
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
dbug: (NA) QPKG: allow unofficial: N/A
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
dbug: (NA) QPKG: require signed: N/A
dbug: (**) QPKG: architecture: i86 (Intel x86)
dbug: (**) QPKG: date Entware installed: 2026-05-10 (Sun 10 May 2026)
dbug: (**) QPKG: Entware type: std
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
dbug: (NA) QPKG: SortMyQPKGs: N/A
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5502: 10#unde: value too great for base (error token is "10#unde")
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 8579: r_nas_firmware_ver: readonly variable
dbug: (NA) QPKG: IncreaseTimeouts: N/A
dbug: (II) ---------------------------------------------------------------------------------------------------------
[~] #
Ah, looks like the QTS compiled for that NAS model doesn’t use the Number key/value. Odd, because I run that same QTS version on my TS-559Pro+ and it does use a Number key/value. I’ll need to add an exception for it.
Give me a day-or-two (I won’t get a chance to look at it today) and I’ll release a new management script to work-around this.
No worries. I’m not in a hurry
Hi mate, I’m deep into some other changes in the management script right-now, and not sure how long it will be until I can fix the issue discussed earlier.
In the meantime, there’s a workaround. If you manually add the missing build number to uLinux.conf, that will stop those errors appearing when running sherpa.
To add it manually, run this in your QTS shell:
setcfg System Number 0468 -f /etc/config/uLinux.conf
It worked like a charm. Thanks!
@FoP, should be fine now in the management script too. Thanks for reporting this. 
It’s actually still showing up a few places. Both on sherpa about and sherpa status
[~] # sherpa about
proc: init ... /share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5538: printf: 0468: invalid number
sherpa v260910-stable (i86)
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5538: printf: 0468: invalid number
dbug: (II) ---------------------------------------------------------------------------------------------------------
dbug: (**) HARDWARE: NAS model: TS-439 Pro II+
dbug: (**) HARDWARE: CPU: Intel(R) Atom(TM) CPU D425 @ 1.80GHz
dbug: (**) HARDWARE: CPU stepping: 10
dbug: (**) HARDWARE: available CPU threads: 2
dbug: (**) HARDWARE: CPU architecture: x86_64 (64b)
dbug: (**) HARDWARE: basic CPU SHA1 benchmark: 39.6MB/s
dbug: (**) HARDWARE: RAM: 0.96GiB
dbug: (**) KERNEL: name: Linux
dbug: (**) KERNEL: version: 3.4.6
dbug: (**) KERNEL: page size: 4kiB
dbug: (**) FIRMWARE: OS: QTS
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5538: printf: 0468: invalid number
dbug: (**) FIRMWARE: version: 4.2.6.0000
dbug: (**) FIRMWARE: build date: 20240618 (Tue 18 Jun 2024)
dbug: (**) FIRMWARE: platform: X86_PINEVIEW
dbug: (**) OS: state: online
dbug: (**) OS: uptime: 9136h:15m:39s
dbug: (**) OS: load averages: 0.56 (1m), 0.22 (5m), 0.25 (15m)
dbug: (**) STORAGE: default volume mounted: /share/MD0_DATA
dbug: (**) STORAGE: basic write benchmark: 168MB/s
dbug: (**) STORAGE: /opt: /share/MD0_DATA/.qpkg/Entware
dbug: (**) USERSPACE: libc: (GNU libc) 2.6.1
dbug: (**) USERSPACE: libc copyright: Copyright (C) 2007 Free Software Foundation, Inc.
dbug: (**) USERSPACE: $EUID: 0
dbug: (NA) USERSPACE: $SUDO_UID: N/A
dbug: (**) USERSPACE: BusyBox version: BusyBox v1.01 (2024.06.17-18:26+0000) multi-call binary
dbug: (**) USERSPACE: BusyBox function count: 133
dbug: (**) SCRIPT: QPKG version: 260906 (Sun 6 Sep 2026)
dbug: (**) SCRIPT: manager version: v260910-stable (i86)
dbug: (**) SCRIPT: manager epoch: 1788994794 (Thu 10 Sep 2026 12:59:54 AM CEST)
dbug: (**) SCRIPT: objects epoch: 1788994789 (Thu 10 Sep 2026 12:59:49 AM CEST)
dbug: (**) SCRIPT: packages epoch: 1788642957 (Sat 5 Sep 2026 11:15:57 PM CEST)
dbug: (**) QPKG: package release: v260906 (Sun 6 Sep 2026)
dbug: (NA) QPKG: allow unofficial: N/A
dbug: (NA) QPKG: require signed: N/A
dbug: (**) QPKG: architecture: i86 (Intel x86)
dbug: (**) QPKG: date Entware installed: 2026-05-10 (Sun 10 May 2026)
dbug: (**) QPKG: Entware type: std
dbug: (WW) QPKG: SortMyQPKGs: not installed
dbug: (NA) QPKG: IncreaseTimeouts: N/A
dbug: (II) ---------------------------------------------------------------------------------------------------------
[~] # sherpa status
proc: init ... /share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5538: printf: 0468: invalid number
sherpa v260910-stable (i86)
/share/MD0_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: line 5538: printf: 0468: invalid number
warn: the Out-Of-Memory killer has been triggered, check for inactive QPKGs.
done: actions complete.
QPKG name: Status: Last action (result): QPKG version: Appl. version: Location:
Entware • enabled, active unsupported 1.03a 1.03a /share/MD0_DATA/.qpkg/Entware
nzbToMedia • enabled, active start (OK) 260906 dynamic /share/MD0_DATA/.qpkg/nzbToMedia
Par2 • enabled, active unsupported 0.8.1.1 0.8.1 /share/MD0_DATA/.qpkg/Par2
SABnzbd • enabled, active start (OK) 260906 dynamic /share/MD0_DATA/.qpkg/SABnzbd
sherpa • enabled, active start (OK) 260906 260906 /share/MD0_DATA/.qpkg/sherpa
SickGear • enabled, active start (OK) 260906 dynamic /share/MD0_DATA/.qpkg/SickGear
• Report information:
'enabled' - QPKG will be started at bootup.
'active' - application is alive (and responsive if a daemon).
'(OK)' - previous action was successful.
'dynamic' - application version is the latest available.
'unsupported' - action tracking is unsupported by this QPKG.
To disable this report information panel:
sherpa report-info off
[~] #