[QPKG] sherpa: a mini-package-manager (CLI) beta
-
- Starting out
- Posts: 10
- Joined: Wed Dec 09, 2015 9:58 pm
Re: [SCRIPT] Sherpa
So, been trying to use this for a couple of days now, using different methods and suggestions,
When I have tried this the error I keep getting is;
[ fail ] QPKG installation failed (Par2cmdline-MT_0.6.14-MT_arm-x41.qpkg) [1]
[ fail ] SABnzbdplus install failed! [21]
Im trying to install on a TS-231 (version 4.3.3) and seeing as Par2cmd isnt offered as X31 I installed Par2.0.6.1.4arm31 instead. I am still getting the same failure though.
I tried editing out the Par2cmd lines from the .sh but this has not helped either.
When I have tried this the error I keep getting is;
[ fail ] QPKG installation failed (Par2cmdline-MT_0.6.14-MT_arm-x41.qpkg) [1]
[ fail ] SABnzbdplus install failed! [21]
Im trying to install on a TS-231 (version 4.3.3) and seeing as Par2cmd isnt offered as X31 I installed Par2.0.6.1.4arm31 instead. I am still getting the same failure though.
I tried editing out the Par2cmd lines from the .sh but this has not helped either.
-
- Getting the hang of things
- Posts: 95
- Joined: Thu Nov 19, 2015 8:44 am
Re: [SCRIPT] Sherpa
When this happens, how will we go about upgrading our sabyenc's?OneCD wrote:@safihre is releasing a new SAB shortly that will require an upgraded sabyenc.
-
- New here
- Posts: 8
- Joined: Thu Aug 20, 2015 9:17 pm
Re: [SCRIPT] Sherpa
Is anyone else getting this error?
[ fail ] Unable to create working directory (/share/Public/sherpa.tmp) [1]
This script has worked for me in the past. I am logged in via SSH with full folder permissions. The share folder /share/Public exists and the files required are located in it. I recently updated my firmware to 4.3.3.0299 20170901. I think it is a firmware issue but if anyone has made it work with this please let me know.
[ fail ] Unable to create working directory (/share/Public/sherpa.tmp) [1]
This script has worked for me in the past. I am logged in via SSH with full folder permissions. The share folder /share/Public exists and the files required are located in it. I recently updated my firmware to 4.3.3.0299 20170901. I think it is a firmware issue but if anyone has made it work with this please let me know.
- OneCD
- Guru
- Posts: 12143
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] Sherpa
Can you please post the complete debug log? I'll need to see what led to this error.Paranor wrote:So, been trying to use this for a couple of days now, using different methods and suggestions,
When I have tried this the error I keep getting is;
[ fail ] QPKG installation failed (Par2cmdline-MT_0.6.14-MT_arm-x41.qpkg) [1]
[ fail ] SABnzbdplus install failed! [21]
Ah, then you may need to revert your changes prior to trying to install it again. It's much more difficult to troubleshoot a bespoke install.Paranor wrote:I tried editing out the Par2cmd lines from the .sh but this has not helped either.
- OneCD
- Guru
- Posts: 12143
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] Sherpa
It's out now.Iceman24 wrote:When this happens, how will we go about upgrading our sabyenc's?OneCD wrote:@safihre is releasing a new SAB shortly that will require an upgraded sabyenc.
viewtopic.php?f=133&t=135929
- OneCD
- Guru
- Posts: 12143
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] Sherpa
I've seen this occur when the installer script is run from the real Public directory (e.g. [/share/MD0_DATA/Public]) instead of the symlinked Public directory [/share/Public]. Can you please confirm that you're running Sherpa in [/share/Public]?IHNSM wrote:Is anyone else getting this error?
[ fail ] Unable to create working directory (/share/Public/sherpa.tmp) [1]
This script has worked for me in the past. I am logged in via SSH with full folder permissions. The share folder /share/Public exists and the files required are located in it. I recently updated my firmware to 4.3.3.0299 20170901. I think it is a firmware issue but if anyone has made it work with this please let me know.
Also, suggest you check permissions for that share. If everything looks OK, then please post the full Sherpa debug log.
-
- New here
- Posts: 8
- Joined: Thu Aug 20, 2015 9:17 pm
Re: [SCRIPT] Sherpa
Thanks for the reply. I checked the share permissions and it is set to read/write for the admin and I tried making it everyone to see if it would work with no luck. The folder does indeed appear to be /share/Public. I am wondering if the latest firmware update made some changes because this just worked for me not long ago and I have not changed any permissions. My Plex server is now having issues as well so it very well may be. I can mount the drive and see all files on every share so I know the files are at least where they should be. Here is the debug log from the most recent attempt after starting the NAS.OneCD wrote:I've seen this occur when the installer script is run from the real Public directory (e.g. [/share/MD0_DATA/Public]) instead of the symlinked Public directory [/share/Public]. Can you please confirm that you're running Sherpa in [/share/Public]?IHNSM wrote:Is anyone else getting this error?
[ fail ] Unable to create working directory (/share/Public/sherpa.tmp) [1]
This script has worked for me in the past. I am logged in via SSH with full folder permissions. The share folder /share/Public exists and the files required are located in it. I recently updated my firmware to 4.3.3.0299 20170901. I think it is a firmware issue but if anyone has made it work with this please let me know.
Also, suggest you check permissions for that share. If everything looks OK, then please post the full Sherpa debug log.
Code: Select all
[ dbug ] (>>) <Init>
[ dbug ] (II) ====================================================================
[ dbug ] (**) SCRIPT: started: Tue Sep 26 01:46:32 PDT 2017
[ dbug ] (**) SCRIPT: file: sherpa.sh
[ dbug ] (**) SCRIPT: version: 2017.06.18b
[ dbug ] (**) SCRIPT: launched as: ./SABnzbdplus
[ dbug ] (**) SCRIPT: target app: SABnzbdplus
[ dbug ] (II) --------------------------------------------------------------------
[ dbug ] (II) Markers: (**) detected, (II) information, (WW) warning, (EE) error,
[ dbug ] (II) (--) done, (>>) function entry, (<<) function exit,
[ dbug ] (II) (vv) variable name & value, ($1) positional argument value.
[ dbug ] (II) --------------------------------------------------------------------
[ dbug ] (**) NAS: model: TVS-1282T
[ dbug ] (**) NAS: firmware version: 4.3.3
[ dbug ] (**) NAS: firmware build: 20170901
[ dbug ] (**) NAS: kernel: 4.2.8 x86_64
[ dbug ] (**) NAS: OS uptime: 22 min
[ dbug ] (**) NAS: system load: 1 min=0.03, 5 min=0.67, 15 min=1.00
[ dbug ] (**) NAS: default volume: /share/CACHEDEV1_DATA
[ dbug ] (**) NAS: $PATH: /opt/bin:/opt/sbin:/bin:/sbin:/usr/bin:/us
[ dbug ] (**) NAS: /opt: /share/CACHEDEV1_DATA/.qpkg/Entware-3x
[ dbug ] (**) NAS: /share/Download: CACHEDEV1_DATA/Download
[ dbug ] (II) --------------------------------------------------------------------
[ fail ] Unable to create working directory (/share/Public/sherpa.tmp) [1]
[ dbug ] (<<) <Init> [2]
[ dbug ] (>>) <Cleanup>
[ dbug ] (<<) <Cleanup> [2]
[ dbug ] (>>) <DisplayResult>
[ fail ] SABnzbdplus install failed! [2]
[ dbug ] (**) SCRIPT: finished: Tue Sep 26 01:46:32 PDT 2017
[ dbug ] (**) SCRIPT: elapsed time: 00h:00m:00s
[ dbug ] (II) ====================================================================
[ dbug ] (<<) <DisplayResult> [2]
- OneCD
- Guru
- Posts: 12143
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] Sherpa
For reference, here's the code related to that error:IHNSM wrote:I checked the share permissions and it is set to read/write for the admin and I tried making it everyone to see if it would work with no luck. The folder does indeed appear to be /share/Public. I am wondering if the latest firmware update made some changes because this just worked for me not long ago and I have not changed any permissions. My Plex server is now having issues as well so it very well may be.
Code: Select all
$MKDIR_CMD -p "$WORKING_PATH" 2> /dev/null
result=$?
if [ "$result" -ne "0" ]; then
ShowError "Unable to create working directory ($WORKING_PATH) [$result]"
errorcode=2
returncode=1
else
cd "$WORKING_PATH"
fi
Code: Select all
ls -lad /share/Public
ls -lad /share/CACHEDEV1_DATA/Public
Code: Select all
[~] # ls -lad /share/Public
lrwxrwxrwx 1 admin administ 15 Jan 1 2002 /share/Public -> MD0_DATA/Public/
[~] # ls -lad /share/MD0_DATA/Public
drwxrwxrwx 2 admin administ 4096 Sep 26 19:21 /share/MD0_DATA/Public/
And finally, try to manually create a directory inside [/share/Public] via the CLI:
Code: Select all
mkdir /share/Public/test; echo $?
-
- New here
- Posts: 8
- Joined: Thu Aug 20, 2015 9:17 pm
Re: [SCRIPT] Sherpa
OneCD wrote:For reference, here's the code related to that error:IHNSM wrote:I checked the share permissions and it is set to read/write for the admin and I tried making it everyone to see if it would work with no luck. The folder does indeed appear to be /share/Public. I am wondering if the latest firmware update made some changes because this just worked for me not long ago and I have not changed any permissions. My Plex server is now having issues as well so it very well may be.Can you please post the output of these?Code: Select all
$MKDIR_CMD -p "$WORKING_PATH" 2> /dev/null result=$? if [ "$result" -ne "0" ]; then ShowError "Unable to create working directory ($WORKING_PATH) [$result]" errorcode=2 returncode=1 else cd "$WORKING_PATH" fi
On my older NAS, this yields:Code: Select all
ls -lad /share/Public ls -lad /share/CACHEDEV1_DATA/Public
Try to reset the permissions for the Public share. Delete it via QTS (tick the box to delete the contents too), then re-create it. But ensure it's empty first.Code: Select all
[~] # ls -lad /share/Public lrwxrwxrwx 1 admin administ 15 Jan 1 2002 /share/Public -> MD0_DATA/Public/ [~] # ls -lad /share/MD0_DATA/Public drwxrwxrwx 2 admin administ 4096 Sep 26 19:21 /share/MD0_DATA/Public/
And finally, try to manually create a directory inside [/share/Public] via the CLI:Code: Select all
mkdir /share/Public/test; echo $?
I got the following results.
Code: Select all
[~] # ls -lad /share/Public
lrwxrwxrwx 1 admin administ 21 Sep 25 18:16 /share/Public -> CACHEDEV1_DATA/Public/
[~] # ls -lad /share/CACHEDEV1_DATA/Public
drwxrwxrwx 5 admin administ 4096 Sep 26 02:48 /share/CACHEDEV1_DATA/Public/
EDIT: I am going to revert back to my previous firmware. This all started after I did that. I'll post back my results. My Plex i still can't seem to get to work either. I can still mount shares remotely on other machines and open the files that way.
- OneCD
- Guru
- Posts: 12143
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] Sherpa
Hmm... that's a noodle-scratcher...IHNSM wrote:I was able to manually create the folder in /share/Public as well.
I can't advise there: I don't run QTS 4.3.x so I've no idea of its restrictions. It's possible to do that in the older QTS 4.2.6.IHNSM wrote:It does not seem to want to let me delete any of the default share names though. Other folders outside of the default it will let me select and delete.
I'll do some research. I seem to remember there being problems with odd behaviour in the shares, but I don't think a solution was found as they kinda resolved themselves.
-
- New here
- Posts: 8
- Joined: Thu Aug 20, 2015 9:17 pm
Re: [SCRIPT] Sherpa
I am now convinced something happened to my shares when I updated my firmware. Reverting back to the previous version did not fix it however. I am not sure how it happened but it is across all shares and folders. I did not lose access to them completely and the files are all intact but for whatever reason I can only access them via file station or through SMB. I can manually add folders via a terminal but no applications or scripts can access them. I guess it may be time for a good old backup and restore. Perhaps a reset with data intact will work. Not going to chance it though . I have around 11TB on there heh.
-
- New here
- Posts: 6
- Joined: Thu Apr 20, 2017 5:06 am
Re: [SCRIPT] Sherpa
The latest version of sabnzbd requires sabyenc 3.3.1+, so I ran your command (but replacing 3.0.2 w/ 3.3.1), no more errors. Cheers!OneCD wrote:Hi and welcome to the forum. Looks like I'll be returning here to help support SABnzbd.
@safihre is releasing a new SAB shortly that will require an upgraded sabyenc.xcabur wrote:sabnzbd.log:Code: Select all
2017-09-20 23:03:38,773::WARNING::[SABnzbd:410] SABYenc disabled: no correct version found! (Found v3.3.1, expecting v3.0.2) 2017-09-20 23:03:38,776::ERROR::[SABnzbd:419] _yenc module... NOT found!
But for now, to fix this on your install, run the following:Code: Select all
pip uninstall sabyenc && pip install sabyenc==3.0.2 && /etc/init.d/sabnzbd.sh restart
- OneCD
- Guru
- Posts: 12143
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: [SCRIPT] Sherpa
Oops - I probably should have put a link here to the announcement thread.intel352 wrote:The latest version of sabnzbd requires sabyenc 3.3.1+, so I ran your command (but replacing 3.0.2 w/ 3.3.1), no more errors. Cheers!
-
- New here
- Posts: 8
- Joined: Thu Aug 20, 2015 9:17 pm
Re: [SCRIPT] Sherpa
I tried one last thing and enabled the guest account and gave it full permissions. It made everything work oddly enough but I still could not get it to work with the regular user or admin account so I gave up on this and just backed up to my spare drives and reinitialized my NAS. Everything works fine now. I wish I could have found a solution in case some others ran into this issue but from what I could tell everything was set properly. Thanks for the assistance.OneCD wrote:Hmm... that's a noodle-scratcher...IHNSM wrote:I was able to manually create the folder in /share/Public as well.
I can't advise there: I don't run QTS 4.3.x so I've no idea of its restrictions. It's possible to do that in the older QTS 4.2.6.IHNSM wrote:It does not seem to want to let me delete any of the default share names though. Other folders outside of the default it will let me select and delete.
I'll do some research. I seem to remember there being problems with odd behaviour in the shares, but I don't think a solution was found as they kinda resolved themselves.
- dirkonline
- Easy as a breeze
- Posts: 305
- Joined: Mon Oct 18, 2010 4:08 pm
Re: [SCRIPT] Sherpa
Seeing the Stephane has updated the Par2 link, I wondered why Sherpa does not install the latest version:
Looking at SABnzbdplus which is called via Sherpa:
and then we have the prefix:
So I reckon what I have to do, is take my downloaded version of Sherpa and change that part in line 1204 to:
Which should then be combined to: for ARM for example
Looking at SABnzbdplus which is called via Sherpa:
Code: Select all
elif [ "$1" == "Par2cmdline-MT" ]; then
if [ "$STEPHANE_QPKG_ARCH" == "x86" ]; then
qpkg_md5="531832a39576e399f646890cc18969bb"
qpkg_url="${Stephane_urlprefix}_x86.qpkg.zip"
elif [ "$STEPHANE_QPKG_ARCH" == "x64" ]; then
qpkg_md5="f3b3dd496289510ec0383cf083a50f8e"
qpkg_url="${Stephane_urlprefix}_x86_64.qpkg.zip"
elif [ "$STEPHANE_QPKG_ARCH" == "x41" ]; then
qpkg_md5="1701b188115758c151f19956388b90cb"
qpkg_url="${Stephane_urlprefix}_arm-x41.qpkg.zip"
Code: Select all
local Stephane_urlprefix="http://www.qoolbox.fr/Par2cmdline-MT_0.6.14-MT"
Code: Select all
local Stephane_urlprefix="http://www.qoolbox.fr/Par2_0.7.4.0"
Code: Select all
http://www.qoolbox.fr/Par2_0.7.4.0_arm-x41.qpkg.zip