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

[Shadytree]

No worries, it's a simple amend anyhow.

Are you able to advise which files and values you needed to update? This would help a lot.

Yes will make a note when i get to that point. I will do via each apps config menu rather than via shell though.

[Shadytree]

No worries, it's a simple amend anyhow.

Are you able to advise which files and values you needed to update? This would help a lot.

Yes will make a note when i get to that point. I will do via each apps config menu rather than via shell though.

No easy way of doing this unfortunately, it was a case of pointing each file to a new folder route.
One thing that did surprise/confuse me is looking through the SAB config, SHERPA installed the QPKGs on a Default Base Folder:

Code: Select all

/share/CACHEDEV1_DATA/.qpkg/SABnzbd/config

, even though I ran Sherpa on /share/public Now the amount of space free showing in SAB is reading the cache rather than the HDD raid storage. Any ideas?

[OneCD]

No easy way of doing this unfortunately, it was a case of pointing each file to a new folder route.

I've been thinking about this and it shouldn't be as big a problem as I first feared. So, now I'm wondering if you're doing something non-standard with the QPKGs on your new NAS?

Can you please provide at-least one example of a path that needed changing? I need to see what file you changed, as well as the folder routes before-and-after.

One thing that did surprise/confuse me is looking through the SAB config, SHERPA installed the QPKGs on a Default Base Folder:

Code: Select all

/share/CACHEDEV1_DATA/.qpkg/SABnzbd/config

, even though I ran Sherpa on /share/public

That's correct. All QPKGs are installed into the default volume QPKG installation directory. This is by-design.

It's not possible to "install" a QPKG in the Public share.

Now the amount of space free showing in SAB is reading the cache rather than the HDD raid storage. Any ideas?

You lost me there. Not sure what you mean.

[Shadytree]

No easy way of doing this unfortunately, it was a case of pointing each file to a new folder route.

I've been thinking about this and it shouldn't be as big a problem as I first feared. So, now I'm wondering if you're doing something non-standard with the QPKGs on your new NAS?

Can you please provide at-least one example of a path that needed changing? I need to see what file you changed, as well as the folder routes before-and-after.

/share/Multimedia/TV
/share/Multimedia/Movies

Now the amount of space free showing in SAB is reading the cache rather than the HDD raid storage. Any ideas?

You lost me there. Not sure what you mean.

Instead of showing the remaining available space at the bottom of the queue window in SAB it shows 0mb free space with a warning !! rather than the 30.09TB that is available

[OneCD]

/share/Multimedia/TV
/share/Multimedia/Movies

Context ... I need context!

• Which file did you modify to make this change?
• What was the variable name in this file?
• Did you decide on a different media folder layout for your new NAS?

Instead of showing the remaining available space at the bottom of the queue window in SAB it shows 0mb free space with a warning !! rather than the 30.09TB that is available

It sounds like you have a cache volume on SSDs and a userdata volume on regular HDDS, and you're currently running SABnzbd on the cache volume - correct?

Have you tried "migrating" the SABnzbd application via your QTS App Center to the userdata volume? https://www.qnap.com/en/how-to/knowledg ... as-volume/

[Shadytree]

Instead of showing the remaining available space at the bottom of the queue window in SAB it shows 0mb free space with a warning !! rather than the 30.09TB that is available

It sounds like you have a cache volume on SSDs and a userdata volume on regular HDDS, and you're currently running SABnzbd on the cache volume - correct?

Have you tried "migrating" the SABnzbd application via your QTS App Center to the userdata volume? https://www.qnap.com/en/how-to/knowledg ... as-volume/

mmmmm odd, there isn't that option on any of my apps, just :

Stop
Remove
Display On > Admin Menu, All users Menu

Do I have to enable somewhere?

I did find a short term fix by moving the incomplete and complete folders to the HDDs

[OneCD]

mmmmm odd, there isn't that option on any of my apps, just :

Stop
Remove
Display On > Admin Menu, All users Menu

Do I have to enable somewhere?

I had to reinit my new NAS and create 2 volumes so I could check this.

It turns-out app volume migration is something that has to be configured in each QPKG at build-time.

I've now enabled volume migration for the SABnzbd app only and released an updated QPKG, but you'll need to upgrade your existing one before you can use it.

Code: Select all

sherpa clean
sherpa upgrade sab

Once this is complete, relaunch your QTS App Center UI, and you should now find the SABnzbd icon drop-down menu has a "migrate to ..." option.

I did find a short term fix by moving the incomplete and complete folders to the HDDs

With regard to space, that will be the only fix. SABnzbd will read the free-space on whichever volumes your folder paths point-to, not the volume SABnzbd is installed on. So, you don't need to migrate SABnzbd unless you really want to.

[Shadytree]

mmmmm odd, there isn't that option on any of my apps, just :

Stop
Remove
Display On > Admin Menu, All users Menu

Do I have to enable somewhere?

I had to reinit my new NAS and create 2 volumes so I could check this.

It turns-out app volume migration is something that has to be configured in each QPKG at build-time.

I've now enabled volume migration for the SABnzbd app only and released an updated QPKG, but you'll need to upgrade your existing one before you can use it.

Code: Select all

sherpa clean
sherpa upgrade sab

Once this is complete, relaunch your QTS App Center UI, and you should now find the SABnzbd icon drop-down menu has a "migrate to ..." option.

I did find a short term fix by moving the incomplete and complete folders to the HDDs

With regard to space, that will be the only fix. SABnzbd will read the free-space on whichever volumes your folder paths point-to, not the volume SABnzbd is installed on. So, you don't need to migrate SABnzbd unless you really want to.

I think that is called, going above and beyond !
I'll see how things go, but is good to know its now possible. Thanks as ever for your unwavering support and dedication

As regards the file directories, I decided to backup my SickChill and SickGear and copy over like you suggested. Saves having to re-add all the media and settings again. So just making sure my paths are matched to my old NAS.

I also thought of a much simpler way of switching control over on the apps from my old NAS to new NAS. Just flip their static IP's ...DOH!

[potestus]

sherpa status eror: A required NAS system file is missing (/bin/less): aborting ...

Any ideas?

[OneCD]

sherpa status eror: A required NAS system file is missing (/bin/less): aborting ...

Any ideas?

What firmware-version and build-number is installed on your NAS?

[potestus]

sherpa status eror: A required NAS system file is missing (/bin/less): aborting ...

Any ideas?

What firmware-version and build-number is installed on your NAS?

version:4.3.3.1432

[OneCD]

version:4.3.3.1432

OK, should be fixed now.

But, you'll need to remove your existing management script manually (as your sherpa installation is presently broken). Use this:

Code: Select all

rm $(getcfg sherpa Install_Path -f /etc/config/qpkg.conf)/cache/sherpa.manager.sh

... then you should be good-to-go.

[potestus]

OK that worked thanks.. what happened?

[OneCD]

Mea culpa. I recently found QTS 4.5.1 includes GNU 'less' and thought maybe I had just not noticed it in the the older QTS versions. So I included a startup test for it, which has promptly shown it's NOT in the older firmwares.

[potestus]

Thank again.. I still install from the github because downloads from the club always fail?