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

[OneCD]

No complaining, sorry if it came across like that I truly appreciate your help!

No worries, you didn't.

* starting (OMedusa):

So, is Medusa starting correctly now?

[dirkonline]

So, is Medusa starting correctly now?

no, it just stops with a different error, there are no more entries after the attempted Git Pull and "starting" it stops

[~] # /etc/init.d/omedusa.sh start
= (OMedusa) is not active
* updating (OMedusa): failed!
= result: 1
= PullGitRepo(): '/opt/lib/git-core/git-remote-https: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory'
* starting (OMedusa):

[OneCD]

no, it just stops with a different error, there are no more entries after the attempted Git Pull and "starting" it stops

OK, let's try reinstalling Entware:

Code: Select all

./sherpa.sh ew

This will restart all sherpa QPKGs afterward.

[dirkonline]

OK, let's try reinstalling Entware:

Code: Select all

./sherpa.sh ew

This will restart all sherpa QPKGs afterward.

On it! and we are back!

Code: Select all

[/share/Public] # ./sherpa.sh ew
sherpa.sh (200216)

[ proc ] testing Internet access ...
[ done ] Internet is accessible            
[ proc ] downloading file (Entware_1.02std.qpkg) ...
[ done ] downloaded file (Entware_1.02std.qpkg)            
[ proc ] uninstalling 'Entware' ...
[ done ] uninstalled 'Entware'            
[ proc ] installing file (Entware_1.02std.qpkg) - this can take a while ...
[ done ] installed file (Entware_1.02std.qpkg)                                    
[ proc ] updating Entware package list ...
[ done ] updated Entware package list            
[ proc ] calculating number and total size of IPKGs required ...
[ done ] 102 IPKGs (79MB) to be downloaded                             
[ proc ] downloading & installing 102 IPKGs ...  100% (79MB/79MB)  done!            
[ done ] downloaded & installed 102 IPKGs             
[ proc ] downloading & installing PIP modules ...
[ done ] downloaded & installed PIP modules             
[ proc ] restarting service 'SABnzbdplus' ...
[ done ] restarted service 'SABnzbdplus'            
[ proc ] restarting service 'OMedusa' ...
[ done ] restarted service 'OMedusa'            


[ done ] 'Entware' has been successfully reinstalled!

Code: Select all

* starting (OMedusa): -------------------- restart requested --------------------
= Mon Feb 17 22:19:07 CET 2020
= (OMedusa) is not active
= (OMedusa) is not active
* updating (OMedusa): OK
= result: 0
= PullGitRepo(): 'Already up to date.'
* starting (OMedusa): OK
= service configured for HTTP port: 7073

[OneCD]

On it! and we are back!

Great!

I don't know why, but some of those opkg apps seem to corrupt each other.

[dirkonline]

On it! and we are back!

Great!

I don't know why, but some of those opkg apps seem to corrupt each other.

Considering none of the previous installs etc. caused error messages, it certainly seems so. Either way, you are my hero once again
I wonder if we could just do a "Common fixes to try" on the first post?

Re-installing Entware DOES seem to help more often than not. Side effect, now my OpenSSL is more current. I wonder, does it makes sense to include an update of the Entware modules when we install / reinstall something via sherpa?

[OneCD]

I wonder if we could just do a "Common fixes to try" on the first post?

It's there, but I'm not sure how many people notice it:

Known issues

• Sometimes, it seems existing installations of Entware can become "difficult" to work with. So, Entware can also be reinstalled, but this should only be used as a last resort. Using:

  Code: Select all

  ./sherpa.sh Entware

  ... will force sherpa to uninstall your existing Entware QPKG, then install a new one. Please note: Entware will be reverted back to default, and only the IPKGs required to support your installed sherpa apps will be installed.

I wonder, does it makes sense to include an update of the Entware modules when we install / reinstall something via sherpa?

That's a good idea. This is now issue #33.

[dirkonline]

I wonder if we could just do a "Common fixes to try" on the first post?

It's there, but I'm not sure how many people notice it:

Known issues

• Sometimes, it seems existing installations of Entware can become "difficult" to work with. So, Entware can also be reinstalled, but this should only be used as a last resort. Using:

  Code: Select all

  ./sherpa.sh Entware

  ... will force sherpa to uninstall your existing Entware QPKG, then install a new one. Please note: Entware will be reverted back to default, and only the IPKGs required to support your installed sherpa apps will be installed.

Now I feel seen <_<
It does makes sense as the last resort like you wrote. The number of things that can go wrong is as high as the number of possible configurations.

I wonder, does it makes sense to include an update of the Entware modules when we install / reinstall something via sherpa?

That's a good idea. This is now issue #33.

Brilliant! I do not think there should be any side effects and especially with modules like Openssl it makes plenty of sense. Thank you for adding that to the issue list

[potestus]

Any idea what's going on here... it killed sickchill?

The problem starts here:

Code: Select all

[5a41d13104cb4e20bc354b046ff55ebf] Verified in 47 seconds, repair is required
[5a41d13104cb4e20bc354b046ff55ebf] Repair failed, not enough repair blocks (100 short)

Without enough blocks, the downloaded files are incomplete and cannot be rebuilt.

Post-processing then continues to try and unpack and process an incomplete release, and it's all downhill from there.

This is expected behaviour.


The fix? You need more Usenet providers on separate backbones.

I have multiple providers and have had incompletes before but they usually just abort..this has never happened before just wondering any flags in nzb post processing?

[OneCD]

I have multiple providers and have had incompletes before but they usually just abort..this has never happened before just wondering any flags in nzb post processing?

You can have incompletes where so much is missing, it's obvious to SABnzbd that there's no point continuing (example: an NZB with no PARs and a single missing article will trigger an abort).

Then there are those (like the one indicated in your runtime output) where the download was mostly present and may have even included some PARs for repair, but not enough to actually fix it. It couldn't be determined until repair time that this was the case.

Code: Select all

Servers
news.tweaknews.eu=625.7 MB

This display shows only a single provider was tried. Your other providers are not shown here. Even if they don't have the required articles, they will still show a very low byte-count if they were queried.

If your failed download handling is correctly configured, it's quite normal to see all the regular post-processing attempts on an unrepairable download. This is necessary so your searcher (for TV shows, movies, etc... ) will know what's going on, will then search for another release and send it to SABnzbd.

[potestus]

I have multiple providers and have had incompletes before but they usually just abort..this has never happened before just wondering any flags in nzb post processing?

You can have incompletes where so much is missing, it's obvious to SABnzbd that there's no point continuing (example: an NZB with no PARs and a single missing article will trigger an abort).

Then there are those (like the one indicated in your runtime output) where the download was mostly present and may have even included some PARs for repair, but not enough to actually fix it. It couldn't be determined until repair time that this was the case.

Code: Select all

Servers
news.tweaknews.eu=625.7 MB

This display shows only a single provider was tried. Your other providers are not shown here. Even if they don't have the required articles, they will still show a very low byte-count if they were queried.

If your failed download handling is correctly configured, it's quite normal to see all the regular post-processing attempts on an unrepairable download. This is necessary so your searcher (for TV shows, movies, etc... ) will know what's going on, will then search for another release and send it to SABnzbd.

Thanks.. failed downloading normally works with sickchill..but for some reason the
Processing killed sickchill each time I tried it forcing me to restart it .I've manually marked it as failed to pull another release.. this is certainly unusual behaviour.. Fingers crossed..

[OneCD]

I've manually marked it as failed to pull another release.. this is certainly unusual behaviour.. Fingers crossed..

To be fair - it's been a bit hit-and-miss lately with SickChill and nzbToMedia. I've had downloads where (apparently) everything worked fine, only the show wasn't put into the correct place. And others where the logs indicated lots of errors, but in the end, the episode was fine and ended-up exactly where it should.

Oh well, let's ride-it-out ...

[Forward Look]

Hi. Is it possible to get one of the old CouchPotato2 .qpkgs ? I am attempting to duplicate my current NAS to another and would like to migrate this legacy installation of CP.

[OneCD]

Is it possible to get one of the old CouchPotato2 .qpkgs ?

Yup!

I've just pushed my local sherpa package archive up to GitHub so previous CP builds are now available.

The last CP QPKG version was 190928.

Supporting Entware IPKGs for it were: 'python python-pyopenssl python-lxml'

To install: SSH into your NAS as the 'admin' user, then:

Code: Select all

cd /share/Public
opkg install python python-pyopenssl python-lxml
curl --insecure --output CouchPotato2_190928.qpkg https://raw.githubusercontent.com/OneCDOnly/sherpa/master/package-archives/CouchPotato2/build/CouchPotato2_190928.qpkg
sh CouchPotato2_190928.qpkg

[potestus]

So any idea why this happened seemingly a one off? I selected a release manually from cp.

/share/MD0_DATA/Qdownload/nzbToMedia/eol.py:147: LifetimeWarning: Python 2.7 is no longer supported.
warnings.warn(msg, LifetimeWarning)
[09:14:44] [INFO]::MAIN: Loading config from [/share/MD0_DATA/Qdownload/nzbToMedia/autoProcessMedia.cfg]
[09:14:44] [INFO]::MAIN: Python v2.7 reached end of life 50 days ago.
[09:14:44] [WARNING]::MAIN: Please upgrade to a more recent Python version.
[09:14:44] [INFO]::MAIN: Checking database structure...
[09:14:44] [INFO]::MAIN: Checking if git needs an update
[09:14:51] [INFO]::MAIN: No update needed
[09:14:51] [INFO]::MAIN: nzbToMedia Version:5a6837759d90285664b3cb596662adb5bfbcb2a2 Branch:master (Linux 3.4.6)
[09:14:58] [INFO]::MAIN: #########################################################
[09:14:58] [INFO]::MAIN: ## ..::[nzbToMedia.py]::.. ##
[09:14:58] [INFO]::MAIN: #########################################################
[09:14:58] [INFO]::MAIN: Script triggered from SABnzbd 0.7.17+
[09:15:01] [ERROR]::MAIN: Category:[*] is not defined or is not enabled. Please rename it or ensure it is enabled for the appropriate section in your autoProcessMedia.cfg and try again.
[09:15:01] [ERROR]::MAIN: A problem was reported in the /share/Qdownload/nzbToMedia/nzbToMedia.py script.
Changing to directory: /share/MD0_DATA/Qdownload/nzbToMedia