no unrar

[Spinux]

I'm using the 20081002-BETA05 (STABLE) script, but it does not unrar my files.
After download I find the rar-files in /download/The_Boy_In_The_Striped_Pyjamas

These are the details from the webinterface. When I unrar the same file on my PC it extracts fine. What am I doing wrong?

Code:

INFO    Thu, 22 Jan 2009 20:43:40 +0000 Completed post-process-script for The_Boy_In_The_Striped_Pyjamas
INFO    Thu, 22 Jan 2009 20:43:40 +0000 Executing post-process-script for The_Boy_In_The_Striped_Pyjamas
INFO    Thu, 22 Jan 2009 20:43:40 +0000 Queueing The_Boy_In_The_Striped_Pyjamas for post-process-script
INFO    Thu, 22 Jan 2009 20:43:40 +0000 Collection The_Boy_In_The_Striped_Pyjamas completely downloaded
INFO    Thu, 22 Jan 2009 20:43:40 +0000 Successfully downloaded The_Boy_In_The_Striped_Pyjamas/The Boy In The Striped Pyjamas.rar
DETAIL    Thu, 22 Jan 2009 20:43:40 +0000 Checking articles for The_Boy_In_The_Striped_Pyjamas/The Boy In The Striped Pyjamas.rar
DETAIL    Thu, 22 Jan 2009 20:43:40 +0000 Successfully downloaded The_Boy_In_The_Striped_Pyjamas/The Boy In The Striped Pyjamas.rar [2/4]
DETAIL    Thu, 22 Jan 2009 20:43:40 +0000 Successfully downloaded The_Boy_In_The_Striped_Pyjamas/The Boy In The Striped Pyjamas.rar [3/4]
DETAIL    Thu, 22 Jan 2009 20:43:40 +0000 Successfully downloaded The_Boy_In_The_Striped_Pyjamas/The Boy In The Striped Pyjamas.rar [4/4]
DETAIL    Thu, 22 Jan 2009 20:43:40 +0000 Successfully downloaded The_Boy_In_The_Striped_Pyjamas/The Boy In The Striped Pyjamas.rar [1/4]

[lordy]

(01-22-2009 10:24 PM)Spinux Wrote:  I'm using the 20081002-BETA05 (STABLE) script, but it does not unrar my files.

Post the unpak.txt file that should be in the same folder.

[Spinux]

(01-23-2009 04:39 AM)ydrol Wrote:  Post the unpak.txt file that should be in the same folder.

I cannot find unpak.txt, only unpak.sh

[garp99]

Please re-edit your post and add the [ code ] tags around the source CODE so that we can see it properly.

[lordy]

@spinux, no need to post the actual script again! Need logs not the unpak.sh script!

If there is no unpak.txt or unpak.log in the same folder as the rar files that means you have a mistake in the
PostProcess setting in nzbget.conf

Try posing ONLY the PostProcess setting from /share/.nzbget/nzbget.conf

[Spinux]

(01-26-2009 10:37 PM)ydrol Wrote:  @spinux, no need to post the actual script again! Need logs not the unpak.sh script!

If there is no unpak.txt or unpak.log in the same folder as the rar files that means you have a mistake in the
PostProcess setting in nzbget.conf

Try posing ONLY the PostProcess setting from /share/.nzbget/nzbget.conf

This is the PostProcess setting:

Code:

##############################################################################
### PAR CHECK/REPAIR AND POSTPROCESSING                                    ###

# Reload Post-processor-queue on start, if it exists (yes, no)
# For this option to work the options "SaveQueue" and "ReloadQueue" must
# be also enabled.
ReloadPostQueue=yes

# How many par2-files to load (none, all, one)
# none - all added par2-files must be automatically paused
# all - all added par2-files must be downloaded
# one - only one main par2-file must be dowloaded and other must be paused
# Paused files remain in queue and should be deleted manually,
# when they not needed anymore
LoadPars=none

# Automatic par-verification (yes, no)
# To download only needed par2-files (smart par-files loading) set also
# the option "loadpars" to "one". If option "loadpars" is set to "all",
# all par2-files will be downloaded before verification and repair starts.
# The option "renamebroken" must be set to "no", otherwise the par-checker
# may not find renamed files and fail
ParCheck=no

# Automatic par-repair (yes, no)
# If option "parcheck" is enabled and "parrepair" is not, the program
# only verifies downloaded files and downloads needed par2-files, but do
# not start repair-process. This is useful if the server does not have
# enough CPU power, since repairing of large files may take too much
# resources and time on a slow computers.
# This option has effect only if the option "parcheck" is enabled
ParRepair=yes

# Use only par2-files with matching names (yes, no)
# If par-check needs extra par-blocks it searches for par2-files
# in download queue, which can be unpaused and used for restore.
# These par2-files should have the same base name as the main par2-file,
# currently loaded in par-checker. Sometimes extra par files (especially if
# they were uploaded from a different poster) have not matching names.
# Normally par-checker does not use these files, but you can allow it
# to use these files by setting "strictparname" to "no".
# This has however a side effect: if NZB-file contains more than one collection
# of files (with different par-sets), par-checker may download par-files from
# a wrong collection. This increases you traffic (but not harm par-check).
# NOTE: par-checker always uses only par-files added from the same NZB-file
# and the option "strictparname" does not change this behavior
StrictParName=yes

# Cleanup download queue after successful check/repair (yes, no)
# Enable this option for automatic deletion of unneeded (paused) par-files
# from download queue after successful check/repair.
# NOTE: before cleaning up the program checks if all paused files are par-files.
# If there are paused non-par-files (this means that you have paused them
# manually), the cleanup will be skipped for this collection.
ParCleanupQueue=yes

# Set path to program, that must be executed after the download of nzb-file
# or one collection in nzb-file (if par-check enabled and nzb-file contains
# multiple collections; see note below for the definition of "collection")
# is completed and possibly par-checked/repaired.
# Arguments passed to that program:
#  1 - path to destination dir, where downloaded files are located;
#  2 - name of nzb-file processed;
#  3 - name of par-file processed (if par-checked) or empty string (if not);
#  4 - result of par-check:
#      0 - not checked: par-check disabled or nzb-file does not contain any
#          par-files;
#      1 - checked and failed to repair;
#      2 - checked and sucessfully repaired;
#      3 - checked and can be repaired but repair is disabled;
#  5 - state of nzb-job:
#      0 - there are more collections in this nzb-file queued;
#      1 - this was the last collection in nzb-file;
#  6 - indication of failed par-jobs for current nzb-file:
#      0 - no failed par-jobs;
#      1 - current par-job or any of the previous par-jobs for the
#          same nzb-files failed;
# NOTE: The parameter "state of nzb-job" is very important and MUST be checked
# even in the simplest scripts.
# If par-check is enabled and nzb-file contains more than one collection
# of files the postprocess-program is called after each collection is completed
# and par-checked. If you want to unpack files or clean up the directory
# (delete par-files, etc.) there are two possibilities, when you can do this:
#  1) you parse the "name of par-file processed" to find out the base name
#     of collection and clean up only files from this collection (not reliable,
#     because par-files sometimes have different names than rar-files);
#  2) or you just check the parameters "state of nzb-job" and "indication of
#     failed par-jobs" and do the processing, only if they are set to "1"
#     (which means, that this was the last collection in nzb-file and all files
#      are now completed) and to "0" (no failed par-jobs) respectively;
# NOTE 2: if the option "ParCheck" is disabled nzbget calls PostProcess
# only once, not after every collection, because the detection of collection
# is disabled in this case;
# NOTE 3: the term "collection" in the above description actually means
# "par-set". To determine what "collections" are present in nzb-file nzbget
# looks for par-sets. If any collection of files within nzb-file does
# not have any par-files, this collection will not be detected.
# For example, for nzb-file containing three collections but only two par-sets,
# the postprocess will be called two times - after processing of each par-set.
# NOTE 4: do not forget to uncomment the next line
PostProcess=/share/.nzbget/unpak.sh

# Allow multiple post-processing for the same nzb-file (yes,no)
# After the post-processing (par-check and call of a postprocess-script) is
# completed, nzbget adds the nzb-file to a list of completed-jobs. The nzb-file
# stays in the list until the last file from that nzb-file is deleted from
# the download queue (it occurs straight away if the par-check was successful
# and the option "ParCleanupQueue" was set).
# So, if there were paused files in queue and they will be unpaused (manually
# or from a post-process-script) nzbget will not post-process nzb-file again.
# This prevents the unwanted multiple post-processing of the same nzb-file.
# But it might be needed if the par-check/-repair are performed not directly
# by nzbget but from a post-process-script.
# NOTE 1: it is recommended to keep the option disabled. You should enable it
# only if it is suggested by a post-process-script's author.
# NOTE 2: by enabling "AllowReProcess" you should disable the option "ParCheck"
# to prevent multiple par-checking.
AllowReProcess=yes

# Set the default message-kind for output received from postprocess-script
# (None, Detail, Info, Warning, Error, Debug).
# NZBGet checks if the line written by the script to stdout or stderr starts
# with special character-sequence, determining the message-kind, e.g.:
# [INFO] bla-bla
# [DETAIL] bla-bla
# [WARNING] bla-bla
# [ERROR] bla-bla
# [DEBUG] bla-bla
# If the message-kind was detected the text is added to log with detected type.
# Otherwise the message becomes the default kind, specified in this option.
PostLogKind=Detail

[lordy]

You'll need to telnet in,

cd to anny folder that has already got downloaded stuff in and type

Code:

/share/.nzbget/unpak.sh "$PWD" "x.nzb" "" 0 1 0

eg.

Code:

cd /share/Download/The_Boy_In_Striped_Pyjamas
/share/.nzbget/unpak.sh "$PWD" "x.nzb" "" 0 1 0

[Spinux]

Thanx for your reply. This is the result after executing the code:

Code:

/share/.nzbget/unpak.sh: line 107: v: not found

This is line 100 to 114 in my unpak.sh

Code:

100  # v 20080831-01
101  #   Sanity check if nzbge did not do any par processing.
102  #   ZBGet , unrar paths set as options.
103  #   Unpacking dpth cnfigurable.
107  #   MediaCenre feature: HTML Logging for viewing in file browser mode.
108  #   MediaCentr feature: Error Status via fake AVI file
109  #   More bug fixes. (Rar Sanity Check)
110  # v 20080828-03
      #   Added better test for ParCheck/_unbroken courtesy Hugbug.
111    v 20080828-02
112  #   Fixed nested unrr bug.
113  #   Added purging of old NZBs
114  # v 20080828-01

Since this seems to point to a version issue, these are the version details of my nzbget installation:

NZBGet version 0.6.0-testing
NZBGet Web Interface v 1.3 (testing 2)
[A110] Firmware 01-17-081023-15-POP-403

[lordy]

not sure where you got the script from but you need to put a '#' at the start of line 111. using a unix compatible editor.
# means the rest of the line is just a comment for information only.
There seem to be a lot of missing characters (did you cut-n- paste or re-type it?)

[speedy55]

The FTP program FlashFXP will also do a great job with editing the nzbget config file.

[Spinux]

(01-30-2009 07:56 PM)ydrol Wrote:  not sure where you got the script from but you need to put a '#' at the start of line 111. using a unix compatible editor.
# means the rest of the line is just a comment for information only.
There seem to be a lot of missing characters (did you cut-n- paste or re-type it?)

@Ydrol
Your remark about the missing characters triggered me. I don't have any idea what caused this. To rule out any mistakes I just downloaded a fresh copy of the unpak.sh script and put it onto my PCH unedited.
This immediately solved the problem!
So thanks for your support and sharp eye!
Also thanks to all other contributers!
Case solved