par not working

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
tarzanboy76
Newbie
Newbie
Posts: 1
Joined: February 6th, 2015, 4:11 am

par not working

Post by tarzanboy76 »

I seem to have a problem where some downloads report the following error;

Code: Select all

Repairing failed, [Errno 2] No such file or directory
Looking through my logs, this seems to be the relevant section;

Code: Select all

Traceback (most recent call last):
  File "/opt/sabnzbd/sabnzbd/newsunpack.py", line 1042, in par2_repair
    setname, joinables, single=single)
  File "/opt/sabnzbd/sabnzbd/newsunpack.py", line 1188, in PAR_Verify
    startupinfo=stup, creationflags=creationflags)
  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
I did some quick googling, and it seems that most people with this error don't have par2 properly installed. However, I've checked that it installed, checked that it is in the path, and checked that it is accessible by the user that sabnzbd runs under.

What else could be causing this problem??
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: par not working

Post by sander »

I would set SAB's logging to "+Debug", let it run again, and then see what the logging says in the 10-20 lines before that traceback. I expect to see the command that caused the traceback.
Post Reply