SABnzbd Forums

I am looking for some help with debugging why unraring always fails after a download.
I get a message to say "At least one file failed to be unpacked, skipping " but if I go to the directory where it downloaded the files (which it has now labeled in the directory name as FAILED) I can run unrar without problem.

It does this on very download I do, looking for some suggestions on how to debug this further

Using 0.4 RC4 on OSX 10.5

Thanks

Paul

Does this happen in all versions? Or just the latest.

You can send your logs to [email protected] and we will have a look.

thanks, sent log files to email

I did see similar problems with previous 0.4 RCs, but didn't spend much time investigating.

Can/will do more!

Thanks for the logs, It looks like the your unrar is not outputting the values sabnzbd expects.

As soon as unpacking starts, sabnzbd uses the output of the unrar process to build up a list of expected files, but instead of a list of files your unrar seems to be returning the value "nice". Not sure why this is the case, going to look into it further.

embarrassingly unrar version 3.6B6, where as having checked the docs you ask for 3.66. Just downloaded 3.71 from rAf's build and trying another download, will let you know

Thanks

humm, did the same thing again, I can see the reference to 'nice' you are referring too. Might give rAf's OSX built version a go

and there was the root of the problem. unrar was in /usr/local/bin, I had a better look at the log file and there it reported it could not find rar, but sabnzbd still started ok and stayed running. I had the same problem with par2 in the past, but in that case sabnzbd would not stay running and the last entry in the system log was the fact it could not find par2. I had all these problems when trying to start using launchctl, which I discovered does not have /usr/local/bin in its path.

Starting from command line worked fine, from launchctl did not, hence my previous discovery of the par2 problem. Never twigged in my brain till you mentioned if unrar was in /usr/bin. This now explains why unrarring had worked at some point, I must have been starting from the command line at that time.

Sorry for the confusion and thanks for helping me find the problem.

We'll make missing unrar and unzip show up as errors in the Connections screen.
Now there's too little indication that these missing programs are missing.

Missing unzip is a warning.
It's not possible to check versions in a portable way.