Logging to /tmp ?

[vbsaltydog]

Ubuntu 10.0.4
Sab Repo
Sab 0.6.6

Why is sab logging to

Code: Select all

/tmp

when the config > folders setting points to

Code: Select all

 ~/.sabnzbd/log

?

[vbsaltydog]

I was investigating the log file path issue along with a larger problem where NONE of my Sab downloads were unpacking successfully despite the fact that I was using the rarlab unrar. I tracked it down to a problem with the file system. Once I used the gparted utility from the Ubuntu Live CD to check/repair the file system, the unpacks started working and Sab started logging to the correct path.

.... correction ..

Sab says unpacking 4/28 or whatever until it finishes and then the directory in the completed folder for the download is full of rar files. If I use the command

Code: Select all

unrar e file.001.rar

then it tries to create the mkv but fails every time with a read error.

I have tried this on many nzbs that unpack correctly on my macbook with an older version of Sab.

[shypike]

Something wrong with unrar or your filesystem.
What else can I say?
It's not possible for SABnzbd to write a RAR file that has subsequent read errors.
It would be different if unrar reported CRC errors.

[vbsaltydog]

I have completely reinstalled Ubuntu 10.0.4 and Sab. I have downloaded several nzbs and they all download, "unpack", and result in directory full of sequentially numbered rar files. When I try to

Code: Select all

sudo e unrar-nonfree first-sequenced-rar-file.rar

unrar gets through a few of the files and then hangs on a read error, resulting in an abort of unrar.

The file system is brand spanking new and so is unrar-nonfree so what could be causing every nzb to do this?

Thank you

[sander]

I have completely reinstalled Ubuntu 10.0.4 and Sab. I have downloaded several nzbs and they all download, "unpack", and result in directory full of sequentially numbered rar files. When I try to

Code: Select all

sudo e unrar-nonfree first-sequenced-rar-file.rar

unrar gets through a few of the files and then hangs on a read error, resulting in an abort of unrar.

The file system is brand spanking new and so is unrar-nonfree so what could be causing every nzb to do this?

Thank you

Why do you run as sudo? Don't do that unless there's a reason for it.
Why do you give sudo an 'e' option? That does not exist.

So: "unrar-nofree x <blabla>". Or: "unrar x <blabla>"

[shypike]

'e' is extract without paths, 'x' is extract with full paths.

BTW: what happens if you transfer the RAR files to a Windows (or OSX) pc
and there try the unpacking?

[vbsaltydog]

Thank you shypike.

I did transfer the files to os x to try to unrar there but os x doesnt use unrar so it was futile. I did download the same nzb via an older version of Sab on os x and it ran perfectly, unpacked, and resulted in an mkv file.