SABnzbd Forums

Version: 0.5.0 beta 5
OS: Vista x64 Ultimate
Install-type: Windows Installer
Skin: Plush
Firewall Software: using router's firewall (latest Tomato firmware, if that makes a difference)
Are you using IPV6? no
Is the issue reproducible? yes
The following bug report did not happen in the latest 0.4 stable release.

Downloaded files are not being moved to the correct folders that I've got set up under Categories.  For example, using the latest 0.4 release of SABnzbd, all TV shows would be moved to the Z:\TV folder on my NAS, but after upgrading to 0.50b5, they are only being moved to the default Completed folder.  This is the error that gets created in the log: The NAS is set to have the hard drives power down after 30 minutes of inactivity, but this happens whether they are awake or not.  The NAS does not have any sort of special read/write permissions either.  If there is any other information that I can provide you, just let me know.

I have the exact same problem,

Version: .0.5.0 beta 5
OS: Windows 7
Install-type: Windows Installer
Skin: Push
IPV6:  No
Reproducable: Yes

Same as the other guy.. Categories are setup to move the finished item to either "Tv Shows" or "Movies" on a mapped drive:

ERROR:
Failed making (Z:\Media Center Content\TV Shows)
ERROR:
Failed making (Z:\Media Center Content\Movies)


This worked in previous version .0.4 stable

Thanks,
mike

Do either of you use the "Sorting" feature?

The only thing I can think of is this:
1. SABnzbd checks if the TV folder is present.
2. The NAS doesn't answer fast enough and the OS says the folder is missing
3. SABnzbd tries to create the folder
4. The NAS doesn't answer fast enough and the OS says it cannot create the folder
5. SABnzbd says it cannot create the folder.

What happens if you do this:
1. wait for the NAS to fall asleep
2. open a command prompt and type "mkdir z:\just-a-test"

Waited until the NAS fell asleep and did a 'md z:\test' and it created the new folder with no problems.  It took about 15 seconds or so for it to complete while the NAS's drives spun up, but it did create the directory.

Try using UNC pathing. \\HOSTNAME\SHARENAME\TV

I had the same issue when running sabnzb as a service, even if I was logged in. This fixed it. 

Thanks!

That fixed the problem. 

mike

Yep, me too.  Thanks!

Weird that it worked fine like that in 0.4 stable though.

arastaf wrote: I had the same issue when running sabnzb as a service, even if I was logged in. This fixed it. 

When a program runs as a service it usually runs under another user account (often "Local System").
In general, sessions running as a service do not inherit mounted drive letters.
This makes using UNC paths a necessity.

shypike wrote:

arastaf wrote: I had the same issue when running sabnzb as a service, even if I was logged in. This fixed it. 

When a program runs as a service it usually runs under another user account (often "Local System").
In general, sessions running as a service do not inherit mounted drive letters.
This makes using UNC paths a necessity.

Right unless they are sent to run as a user. Either way UNC pathing works just fine, and in most cases is better anyways. Plus its not the fault of the program its a limitation of how windows works.

arastaf wrote:

shypike wrote:

arastaf wrote: I had the same issue when running sabnzb as a service, even if I was logged in. This fixed it. 

When a program runs as a service it usually runs under another user account (often "Local System").
In general, sessions running as a service do not inherit mounted drive letters.
This makes using UNC paths a necessity.

Right unless they are sent to run as a user. Either way UNC pathing works just fine, and in most cases is better anyways. Plus its not the fault of the program its a limitation of how windows works.

I'm not faulting the program in any way, and I'm super happy that the UNC pathing works fine, and like you said, is probably better anyways.  All I'm saying is that using mapped drive letters to my NAS worked perfectly under 0.4.9 stable and I'm running the 0.5 beta in the exact same way I was with the stable release.

I'm having the same problem, but under Ubuntu (XBMC Live).  I have sabnzbd set to unpack files to my QNAP NAS.  I'm using autofs to mount these shares.  If the NAS is completely awake, this works just fine. However, if the harddrives have spundown, then the copy fails with the "Failed making" error, and the file remains on the local XBMC hdd.

Any thoughts on how to fix this?  Thanks!

If the operating system doesn't gracefully handle the
wakeup of the NAS, what can SABnzbd do about this?

snubz wrote: ... under Ubuntu (XBMC Live).  I have sabnzbd set to unpack files to my QNAP NAS.  I'm using autofs to mount these shares.  If the NAS is completely awake, this works just fine. However, if the harddrives have spundown, then the copy fails with the "Failed making" error, and the file remains on the local XBMC hdd.

For anyone with this issue, I fixed it by mounting my NAS shares using NFS instead of SMB (and using fstab instead of autofs, but seems to be the NFS that actually did the trick).

And yup, not a sabnzb prob, but an OS thing.