The par2 check and repair will fail, if the paths (as specified in the config tab) are in UNC format.
If I map the same paths to drive-letters before, it does work fine.
(Win32 client, version 0.4.4.)
par2 failed on UNC paths
Forum rules
Help us help you:
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.
Re: par2 failed on UNC paths
What sort of path are you giving it?
\\ComputerName\SharedFolder\Resource
smb://ComputerName/SharedFolder/Resource
\\?\UNC\ComputerName\SharedFolder\Resource
Does sabnzbd have access to this path? If you are downloading to an another PC I recommend having the incomplete folder hosted on the local filesystem and just the complete folder listed externally.
What sort of error do you get back? Just an unammed par2 error?
\\ComputerName\SharedFolder\Resource
smb://ComputerName/SharedFolder/Resource
\\?\UNC\ComputerName\SharedFolder\Resource
Does sabnzbd have access to this path? If you are downloading to an another PC I recommend having the incomplete folder hosted on the local filesystem and just the complete folder listed externally.
What sort of error do you get back? Just an unammed par2 error?
Re: par2 failed on UNC paths
It's quite simple. The par2.exe program does not support UNC paths.Munters wrote: The par2 check and repair will fail, if the paths (as specified in the config tab) are in UNC format.
This is outside of our control.
Re: par2 failed on UNC paths
True. The par2 utility is supplied silently within the sabnzbd package.however.
It would be nice sabnzbd would give a warning if someone uses UNC paths in the configuration,
as long as the supplied par2 checking utility doesn't support UNC paths.
Now the "complete package" does not work, without an understandable error or something.
It would be nice sabnzbd would give a warning if someone uses UNC paths in the configuration,
as long as the supplied par2 checking utility doesn't support UNC paths.
Now the "complete package" does not work, without an understandable error or something.
Re: par2 failed on UNC paths
I agree, some path validation and warning could be done.
Filed as ticket #138, scheduled for release 0.4.5.
Filed as ticket #138, scheduled for release 0.4.5.
Last edited by shypike on September 25th, 2008, 5:20 am, edited 1 time in total.
Re: par2 failed on UNC paths
Any chance of integrating QuickPar? As it supports unc paths.
Re: par2 failed on UNC paths
Impossible, QuickPar is GUI only. It has no command line interface, nor a API.
It's also closed source, meaning no one but author can improve it, something which he
is obviously not doing.
It's also closed source, meaning no one but author can improve it, something which he
is obviously not doing.