Issues Downloading/Unpacking to a Network Drive

[Corbet]

Setup: 10.7 Lion with the latest version of sabnzbd. Asus RT-N56U Router with a NTFS-formatted drive attached with SMB. I am using Paragon NTFS to enable write access to the NTFS drive.

I have a networked drive that I can read and write to with no issue in finder. I tried setting my complete folder to a location on the networked drive and in the download section, it shows the correct hard drive space remaining and doesn't give me any errors. After I download a file and it attempts to unpack it on the network drive, the items will show up as "complete" and say it's being moved, but when I go into the complete folder on the networked drive, the item's folder is there but it doesn't contain any of the actual files. If I go into the incomplete folder on the computer running sabnzbd, the downloaded file is complete in it.

I also get this error:
Error removing workdir (" ")

If I set my incomplete path to the networked drive, the Download immediately fails and I get:

» URL Fetching failed; Unusable NZB file, Try again

So here's the thing: if I set the path to incomplete and complete folders to the computer running sabnzbd and have something like SickBeard run a script to move the file over to the networked drive, Sickbeard has no problems moving the files over.

Does anyone have any ideas why sabnzbd isn't playing nice with my networked drive but sickbeard and finder do? Any ideas?

[shypike]

Can you set the logging level to "debug" on the Status page
and replay a failing scenario?
After that get the log file from the Status page and email it
to bugs at sabnzbd.org
I recommend to have the "incomplete" drive locally anyway.

[HeyBoff]

I went ahead and forwarded my log file. If anyone else is curious to see what it's spitting out, here's what it gave me when I replicated the issue:


2011-08-07 17:52:20,960::INFO::[postproc:529] Par2 check finished on BLAHBLAH
2011-08-07 17:52:20,985::INFO::[misc:718] Creating directories: /volumes/AiDisk_a2/Usenet/Complete/BLAHBLAH
2011-08-07 17:52:20,991::ERROR::[misc:720] Failed making (/volumes/AiDisk_a2/Usenet/Complete/BLAHBLAH
2011-08-07 17:52:20,991::ERROR::[postproc:444] Post Processing Failed for BLAHBLAH
(Cannot create final folder /volumes/AiDisk_a2/Usenet/Complete/BLAHBLAH)

[shypike]

From you logging, I'd say that OSX has an issue with the external drive.
The logging says:

Code: Select all

IOError: [Errno 13] Permission denied: '/volumes/AiDisk_a2/Usenet/_UNPACK_BlaBla/BlaBla - Bla [1986].mp3'

Given that the Python interpreter is also Apple's, it's an Apple problem.

How do you run SickBeard? They don't have an DMG distribution.
The reason I ask is because if you run it using the native OSX Lion Python interpreter,
that might explain why it doesn't have problems with the drive.
We're still using the Snow Leopard Python framework.

[HeyBoff]

From you logging, I'd say that OSX has an issue with the external drive.
The logging says:

Code: Select all

IOError: [Errno 13] Permission denied: '/volumes/AiDisk_a2/Usenet/_UNPACK_BlaBla/BlaBla - Bla [1986].mp3'

Given that the Python interpreter is also Apple's, it's an Apple problem.

How do you run SickBeard? They don't have an DMG distribution.
The reason I ask is because if you run it using the native OSX Lion Python interpreter,
that might explain why it doesn't have problems with the drive.
We're still using the Snow Leopard Python framework.

When I made the jump to Lion, my initial installation of SickBeard was giving me errors (I originally used the instructions from here: http://www.jetshred.com/2010/05/13/inst ... c-os-10-6/).

I went ahead and installed sickbeard from scratch, using the same insturctions as before and it worked fine, so I assume I'm using the Lion Python framework, not Snow Leopard.

Is it possible to manually install sabnzbd with the new Lion Python Framework? Will sabnzbd transition to that framework in the future?

[shypike]

OK, you're using the native Python interpreter from Lion for SickBeard.
I'm afraid you'll have to wait until we can create a DMG based on Lion's Python.
I'm almost sure that the problem is in differences between SnowLeopard's Python and Lion's.
You could run SABnzbd in the same way as SickBeard,
however you'd need to compile the yEnc module, which requires XCode 4.2 installed.

[HeyBoff]

OK, you're using the native Python interpreter from Lion for SickBeard.
I'm afraid you'll have to wait until we can create a DMG based on Lion's Python.
I'm almost sure that the problem is in differences between SnowLeopard's Python and Lion's.
You could run SABnzbd in the same way as SickBeard,
however you'd need to compile the yEnc module, which requires XCode 4.2 installed.

Thanks for all your help, I have a couple more questions: Do you have any idea if there are plans to create a DMG based on Lion's Python instead of Snow Leopard?

Secondly, can you please point me into the right direction in regards to compiling the yEnc module? I have XCode 4.2 installed.

[shypike]

Basically, just download the yenc tarbal file from SourceForge.
Unpack it somewhere and run this in a terminal:
sudo python setup.py install
It will compile and install yEnc as part of the Python framework.

http://sourceforge.net/projects/sabnzbd ... /yEnc-0.3/

Please let me know if this solves the issue.

[HeyBoff]

Still haven't figured it out. I went ahead and made sure I had Xcode 4.2 installed, I installed yEnc, and I downloaded and tried SABnzbd-0.6.7-osx-src.tar.gz and SABnzbd-0.6.7-src.tar.gz.

I cd'd into the sabnzbd folder and ran it, but was still unable to write to the network drive. I e-mailed another log file. Am I doing something wrong? Did I download the wrong sabnzbd source file?

[shypike]

As you can see in the log, things go wrong in the Python runtime library.
The error is "no access".
Which value (if any) did you set Config->Folders->Permissions ?
This value is also used in the initial creation of folders.
If you have a value in now, maybe it's better to remove it, because then defaults are used.

NTFS has a completely different access control method than HFS+ and I have no idea
how the two are mapped by Paragon. Also under Windows, NTFS has a hassle-free inheritance system,
which will make any new content of a folder inherit access rights from that folder.
I don't know how that's implemented on your NTFS drive.