Problem with... Dont know where to search

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
thefox154
Newbie
Newbie
Posts: 2
Joined: January 4th, 2013, 4:29 am

Problem with... Dont know where to search

Post by thefox154 »

First of all im completely new to Sab and Nasses. But i (believe) i succesfully installed Sabnzbd 0.6.15 on my Zyxel NSA320.
When a download is 100% complete is extracts etc and i can watch.

But (as i suppose is the problem) when a file is not complete sab doesn't do anything about this. Par etc is checked in menu options.
Sab moves the download to the history. And i can hit Retry if i want to. In this case the par files aren't downloaded but are needed.
When i hit retry the nzb moves to the download screen. When i hit the download is get this error.
If i wait a couple of secondes the download file is back to the history and is failed again. I tried other downloads, but they all give the same problem when par is needed.

Does this sound fimiliar to your guys or does someone have a tip or trick?


500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
Traceback (most recent call last):
File "/usr/local/zy-pkgs/ffproot/ffp/bin/sabnzbd/cherrypy/_cprequest.py", line 618, in respond
cherrypy.response.body = self.handler()
File "/usr/local/zy-pkgs/ffproot/ffp/bin/sabnzbd/cherrypy/_cpdispatch.py", line 25, in __call__
return self.callable(*self.args, **self.kwargs)
File "/usr/local/zy-pkgs/ffproot/ffp/bin/sabnzbd/sabnzbd/interface.py", line 489, in default
return template.respond()
File "_ffp_bin_sabnzbd_interfaces_Plush_templates_nzo_tmpl.py", line 104, in respond
NotFound: cannot find 'filename' while searching for 'slot.filename'
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Problem with... Dont know where to search

Post by shypike »

You are running an older version of SABnzbd and the 500 error
shows up when the job has left the queue.
This problem has been fixed in later releases, but does not affect functionality.

par2 files are masked in the list until SABnzbd has determined that they need to
be downloaded, which is after the first failed verification.
The job will then be sent back to the download queue.
thefox154
Newbie
Newbie
Posts: 2
Joined: January 4th, 2013, 4:29 am

Re: Problem with... Dont know where to search

Post by thefox154 »

Thanks for you fast response. I will google and learn how to update to a new version.

Until then i dont have any thoughts about what is going wrong at this moment.
My downloads go to the history. There is a little red icon with a death-head in front of it. Hitting retry doenst solve anything. Sabnzbd has download the necessary .par files.
When i go to my incomplete download folder and copy all the files downloaded to my pc and run quickpar it has enough blocks and quickpar can repair my downloaded files. My nas doesn't.. ???
Is there something i am missing in Sabnzbd???

Edit:
When i turn off the checkbox Post-Process Only Verified Jobs / Only perform post-processing on jobs that passed all PAR2 checks, Sab starts extracting those jobs. Does this mean that something isn't installed correctly? Supposedly it should do all the checks?
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Problem with... Dont know where to search

Post by shypike »

You need to upgrade your SABnzbd version.
Nowadays many posts have weird naming that older versions
of SABnzbd cannot handle.
Post Reply