[QPKG] sherpa: a mini-package-manager (CLI) beta
-
- New here
- Posts: 5
- Joined: Fri Mar 13, 2020 1:11 am
Re: [SCRIPT] sherpa.sh
I updated my post before.
The actual package that's being downloaded when I initiate the install is par2cmdline_0.8.0-1_armv7-3.2.ipk
Here's the output of your command above:
sh Par2_0.8.0.0_arm-x41.qpkg
Install QNAP package on TS-NAS...
Par2_0.8.0.0_arm-x41.qpkg: line 63: set_progress_fail: command not found
The actual package that's being downloaded when I initiate the install is par2cmdline_0.8.0-1_armv7-3.2.ipk
Here's the output of your command above:
sh Par2_0.8.0.0_arm-x41.qpkg
Install QNAP package on TS-NAS...
Par2_0.8.0.0_arm-x41.qpkg: line 63: set_progress_fail: command not found
- OneCD
- Guru
- Posts: 12163
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] sherpa.sh
Yes, that IPK is fine as a last resort, but it's not the multi-thread version available via the QPKG. If we can get the QPKG version running, it should be quicker on CPUs that support multi-threading. Your AL-212 is a dual-core CPU so it should benefit from having a multi-threaded Par2 binary.
Thank you. This is a problem I've just asked the Par2 QPKG maintainer about. I'll post back here when we have a solution.
- OneCD
- Guru
- Posts: 12163
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] sherpa.sh
@straw, can you please run this on your NAS and post the result?
Code: Select all
getcfg "" Platform -f /etc/platform.conf
- dirkonline
- Easy as a breeze
- Posts: 305
- Joined: Mon Oct 18, 2010 4:08 pm
Re: [SCRIPT] sherpa.sh
Just for the record: I have an TS-431+ and the command output is:OneCD wrote: ↑Fri Mar 13, 2020 11:40 am@straw, can you please run this on your NAS and post the result?Code: Select all
getcfg "" Platform -f /etc/platform.conf
Code: Select all
[~]
# getcfg "" Platform -f /etc/platform.conf
ARM_AL
-
- New here
- Posts: 5
- Joined: Fri Mar 13, 2020 1:11 am
Re: [SCRIPT] sherpa.sh
Amen dirkonline.
Here's the output:
[/share/Download/complete] # getcfg "" Platform -f /etc/platform.conf
ARM_MS
Here's the output:
[/share/Download/complete] # getcfg "" Platform -f /etc/platform.conf
ARM_MS
- OneCD
- Guru
- Posts: 12163
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] sherpa.sh
Thanks Dirk.dirkonline wrote: ↑Fri Mar 13, 2020 8:27 pm Just for the record: I have an TS-431+ and the command output is:
Code: Select all
[~] # getcfg "" Platform -f /etc/platform.conf ARM_AL
So, I think that means @straw's model is a TS-431P2.
- OneCD
- Guru
- Posts: 12163
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] sherpa.sh
Thanks @straw, I've posted this in the Par2 topic.
-
- Starting out
- Posts: 13
- Joined: Wed May 11, 2011 10:14 pm
Re: [SCRIPT] sherpa.sh
Hello everyone,
hello OneCD,
first of all: @OneCD: thank you very much for all your hard work. I love your script and been using it from day #1 i think. Much appreciated!
I'm using a QNAP TS-431P as of right now. I started with a very old QNAP Model and been moving on from each firmware to the next and upgraded my QNAPs accordingly. And i'm pretty sure, that this will be my main problem. But maybe, someone has the easy fix at hand
I stumbled upon the OWatcher3 Problem and hoped, that the new sherpa-script would solve the downgrade issue for me. It actually didn't. I then turned to the mini-script-snipplet and it didn't work - and that made me look into my system, mostly the PATH Variable.
i noticed, that grep had an issue with the "-o" option, which lead me to the BusyBox Binary and look at this: it wasn't the real grep / find and so on - it was the busybox link which lacks some basic stuff. so i've installed grep via opkg in its full glory
my workaround was to edit the /etc/profile - i've added /opt/bin and /opt/sbin to the PATH Variable right in front of every other path, still no success - so i hardcoded the grep binary into the mini-sniplet and here we go, OWatcher3 is running.
i'm pretty sure, that this is an entware-PATH-problem situation, but maybe, anyone in here has an idea on how to fix this? Where did it screw up my system (.... well, i started around 2010? ... there has to be some garbage left in the QNAP system..)
Thanks for any hints!
Best regards,
redmercury2006
hello OneCD,
first of all: @OneCD: thank you very much for all your hard work. I love your script and been using it from day #1 i think. Much appreciated!
I'm using a QNAP TS-431P as of right now. I started with a very old QNAP Model and been moving on from each firmware to the next and upgraded my QNAPs accordingly. And i'm pretty sure, that this will be my main problem. But maybe, someone has the easy fix at hand
I stumbled upon the OWatcher3 Problem and hoped, that the new sherpa-script would solve the downgrade issue for me. It actually didn't. I then turned to the mini-script-snipplet and it didn't work - and that made me look into my system, mostly the PATH Variable.
i noticed, that grep had an issue with the "-o" option, which lead me to the BusyBox Binary and look at this: it wasn't the real grep / find and so on - it was the busybox link which lacks some basic stuff. so i've installed grep via opkg in its full glory
my workaround was to edit the /etc/profile - i've added /opt/bin and /opt/sbin to the PATH Variable right in front of every other path, still no success - so i hardcoded the grep binary into the mini-sniplet and here we go, OWatcher3 is running.
i'm pretty sure, that this is an entware-PATH-problem situation, but maybe, anyone in here has an idea on how to fix this? Where did it screw up my system (.... well, i started around 2010? ... there has to be some garbage left in the QNAP system..)
Thanks for any hints!
Best regards,
redmercury2006
- OneCD
- Guru
- Posts: 12163
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] sherpa.sh
Hi!
Good pickup. I forgot to specify the QTS 'grep' in the new Python3 "downgrade" function, and that caused the problem you experienced. I've now created this as issue #34 and will work on it this weekend.redmercury2006 wrote: ↑Fri Mar 20, 2020 12:53 am i noticed, that grep had an issue with the "-o" option, which lead me to the BusyBox Binary and look at this: it wasn't the real grep / find and so on - it was the busybox link which lacks some basic stuff. so i've installed grep via opkg in its full glory
Thanks for reporting this!
-
- Starting out
- Posts: 13
- Joined: Wed May 11, 2011 10:14 pm
Re: [SCRIPT] sherpa.sh
nice one, OneCD. Thank you very much!
i'm actually little bit proud of myself, that i discovered this one.. /offtopic
now i'm working on the autopost-process watcher stuff...
i'm actually little bit proud of myself, that i discovered this one.. /offtopic
now i'm working on the autopost-process watcher stuff...
-
- Starting out
- Posts: 29
- Joined: Wed Aug 09, 2017 1:58 am
Re: [SCRIPT] sherpa.sh
Hello there.
THANK you thousand times for your work and efforts !!
Last time i istalled manualley Par2, entware-ng, qpython2 and qsabnzbd from qnabclub.
This worked for me not perfekt (but worked). The sabnzbd Server crashed 2 times a day and needs to be restarted...
Now after a complete reset and total new install of my NAS - i want to do a clean fresh install of sabnzbd via this wonderful sherpa script
I followed the instruction in the first Post of this Thread and installed the SABnzbd Package via
Everything works great - sherpa.sh installed some apps and i can see SABnzbd on my qnap desctop.
But i can not start the server... only get "ERR_CONNECTION_REFUSED"... stop and restart the server will not help.
Sherpa installes following apps. Are there anything missing (Python?)
What is my mistake (sure it is MY mistake - but mybe someone can help me?).
I do not need any other apps - just want to run sabnzbd and its settings on my NAS.
Thank you very much
THANK you thousand times for your work and efforts !!
Last time i istalled manualley Par2, entware-ng, qpython2 and qsabnzbd from qnabclub.
This worked for me not perfekt (but worked). The sabnzbd Server crashed 2 times a day and needs to be restarted...
Now after a complete reset and total new install of my NAS - i want to do a clean fresh install of sabnzbd via this wonderful sherpa script
I followed the instruction in the first Post of this Thread and installed the SABnzbd Package via
Code: Select all
./sherpa.sh SABnzbd
But i can not start the server... only get "ERR_CONNECTION_REFUSED"... stop and restart the server will not help.
Sherpa installes following apps. Are there anything missing (Python?)
What is my mistake (sure it is MY mistake - but mybe someone can help me?).
I do not need any other apps - just want to run sabnzbd and its settings on my NAS.
Thank you very much
You do not have the required permissions to view the files attached to this post.
- OneCD
- Guru
- Posts: 12163
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] sherpa.sh
Hi!
Can you please post the SABnzbd init log? This is a log that records the launch of SABnzbd. I'm guessing there's an issue preventing SAB from starting correctly.Kamikaze01 wrote: ↑Sun Mar 22, 2020 4:45 pm But i can not start the server... only get "ERR_CONNECTION_REFUSED"... stop and restart the server will not help.
To view it:
Code: Select all
cat /var/log/SABnzbdplus.log
-
- Starting out
- Posts: 29
- Joined: Wed Aug 09, 2017 1:58 am
Re: [SCRIPT] sherpa.sh
WOW !!!
Thank u OneCD for this quick answer.
THIS is support
Here is the log
BUT just recognised that when i start the server via IP instead of URL, it worked like a charme.
So i think this must be my problem
Thank you very much OneCD !!!
Thank you thausand times for your work !!!
/edit;
is it possible to change the port 8800 to another port?
If i try to change the port via the gui in sabnzbd and restart the server, i can not reach it any more (old and new port)
Thank u OneCD for this quick answer.
THIS is support
Here is the log
Code: Select all
[~] # cat /var/log/SABnzbdplus.log
-------------------- start requested --------------------
= Sun Mar 22 09:24:34 CET 2020
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
= result: 0
= PullGitRepo(): 'Cloning into '/share/CACHEDEV1_DATA/.qpkg/SABnzbdplus/SABnzbdplus'...
Already up to date.'
* updating language support (SABnzbdplus): OK
= result: 0
= UpdateLanguages(): 'Email MO files
Compile locale/da/LC_MESSAGES/SABemail.mo
Compile locale/de/LC_MESSAGES/SABemail.mo
Compile locale/en/LC_MESSAGES/SABemail.mo
Compile locale/es/LC_MESSAGES/SABemail.mo
Compile locale/fi/LC_MESSAGES/SABemail.mo
Compile locale/fr/LC_MESSAGES/SABemail.mo
Compile locale/he/LC_MESSAGES/SABemail.mo
Compile locale/nb/LC_MESSAGES/SABemail.mo
Compile locale/nl/LC_MESSAGES/SABemail.mo
Compile locale/pl/LC_MESSAGES/SABemail.mo
Compile locale/pt_BR/LC_MESSAGES/SABemail.mo
Compile locale/ro/LC_MESSAGES/SABemail.mo
Compile locale/ru/LC_MESSAGES/SABemail.mo
Compile locale/sr/LC_MESSAGES/SABemail.mo
Compile locale/sv/LC_MESSAGES/SABemail.mo
Compile locale/zh_CN/LC_MESSAGES/SABemail.mo
Create email templates from MO files
Create email template for da
Create email template for de
Create email template for es
Create email template for fi
Create email template for fr
Create email template for he
Create email template for nb
Create email template for nl
Create email template for pl
Create email template for pt_BR
Create email template for ro
Create email template for ru
Create email template for sr
Create email template for sv
Create email template for zh_CN
Main program MO files
Compile locale/da/LC_MESSAGES/SABnzbd.mo
Compile locale/de/LC_MESSAGES/SABnzbd.mo
Compile locale/en/LC_MESSAGES/SABnzbd.mo
Compile locale/es/LC_MESSAGES/SABnzbd.mo
Compile locale/fi/LC_MESSAGES/SABnzbd.mo
Compile locale/fr/LC_MESSAGES/SABnzbd.mo
Compile locale/he/LC_MESSAGES/SABnzbd.mo
Compile locale/nb/LC_MESSAGES/SABnzbd.mo
Compile locale/nl/LC_MESSAGES/SABnzbd.mo
Compile locale/pl/LC_MESSAGES/SABnzbd.mo
Compile locale/pt_BR/LC_MESSAGES/SABnzbd.mo
Compile locale/ro/LC_MESSAGES/SABnzbd.mo
Compile locale/ru/LC_MESSAGES/SABnzbd.mo
Compile locale/sr/LC_MESSAGES/SABnzbd.mo
Compile locale/sv/LC_MESSAGES/SABnzbd.mo
Compile locale/zh_CN/LC_MESSAGES/SABnzbd.mo
Remove temporary templates'
* updating (nzbToMedia): OK
= result: 0
= PullGitRepo(): 'Cloning into '/share/Download/nzbToMedia'...
Already up to date.'
* starting (SABnzbdplus): OK
= service configured for HTTP port: 8800
-------------------- stop requested --------------------
= Sun Mar 22 09:30:21 CET 2020
= (SABnzbdplus) is active
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 2 seconds
-------------------- start requested --------------------
= Sun Mar 22 09:30:39 CET 2020
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
= result: 0
= PullGitRepo(): 'Already up to date.'
* updating (nzbToMedia): OK
= result: 0
= PullGitRepo(): 'Already up to date.'
* starting (SABnzbdplus): OK
= service configured for HTTP port: 8800
[~] #
So i think this must be my problem
Thank you very much OneCD !!!
Thank you thausand times for your work !!!
/edit;
is it possible to change the port 8800 to another port?
If i try to change the port via the gui in sabnzbd and restart the server, i can not reach it any more (old and new port)
- OneCD
- Guru
- Posts: 12163
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] sherpa.sh
Good work.Kamikaze01 wrote: ↑Sun Mar 22, 2020 5:27 pm BUT just recognised that when i start the server via IP instead of URL, it worked like a charme.
So i think this must be my problem
Yes, I've included some code to support this, but it only runs when the SABnzbd QPKG is 'started'.Kamikaze01 wrote: ↑Sun Mar 22, 2020 5:27 pm /edit;
is it possible to change the port 8800 to another port?
If i try to change the port via the gui in sabnzbd and restart the server, i can not reach it any more (old and new port)
So, you'll need change the port number in SABnzbd, then 'stop' and 'start' the SABnzbd QPKG in your App Center to update QTS with the new port number.
Then refresh your App Center web-page to reload the [/etc/config/qpkg.conf] file.