SABnzbd Forums

Hello all,

This is my first post to the forum.  I've been an SABnzbd user and evangelist for about a year now.  I've converted a number of my friends, and we all couldn't be happier.  I just want to take a moment to thank everyone who works on this project and also everyone who contributes their time on this forum. 

As the first SABnzbd user, I unfortunately have to play the role of "tech support" for my converted friends.  I came across something on my buddy's setup last night that I can't figure out.  We did make some changes to his network setup, and I mght have messed up a setting, but I can't figure out how to fix what I'm seeing.  Any help you all can provide would be most appreciated.

The setup below is running SABnzbd v0.5.0.  It's running on an old Mac G5 running Leopard 10.5.x. 

So what's happening is _Unpack folders are starting to show up in the Complete folder.  I understand the process of Incomplete > _Unpack > Rename > Move to complete (or something like that), and I've seen the _Unpack folders when they exist temporarily.  However, I've never seen them show up and remain in the Complete folder.

So we see this happen when we download an NZB from Binsearch and then upload to SABnzbd via the Web interface or via a watched folder.  An example is a Binsearch NZB that contains references to several other NZBs (e.g. multiple episodes of a TV show).  SABnzbd will successfully fetch the underlying NZBs and add them to the queue, and then download the RARs/PARs and process as expected.  That works fine and the requested content ends up in the right place in the Complete folder (respecting sorting, categories, etc).  But what's strange is that NZBs that SABnzbd fetched show up in both the NZB backup folder (which I have enabled) AND in an _UnpackXXX folder in the complete folder.  Why is SABnzbd suddenly keeping these NZBs around?  And why isn't it deleting the temporary _Unpack folders?  Is there a setting that needs to be applied?  I'm not sure what we changed that is causing this.  I've set up several SABnzbd instances, and this is the first time I'm seeing this.

Usually file deletions and folder renames/deletions fail because the OS doesn't allow it (at that moment).
Virus-scanners are another source of trouble, but OSX users don't have these
The primary NZB job must have the +D setting, otherwise files remain behind.

What can help is to set the clean-up list (Config->General) to include NZB files.
Don't worry, they will still be re-queued.

We haven't tested this feature for a while, so time to give it some attention.

Ah.  That makes sense.  So the previous Incomplete/Complete directories were on an external hard drive.  And we had to move everything to a directory on the local computer (because the external hard drive died).  I'm guessing it has something to do with file permissions, then?  Perhaps the external hard drive was set to ignore file permissions for the disk volume.  We're now trying to download everything to /Users/username/Movies/Media/Complete.  Do you think this has something to do with the fact that this is a sub-directory of my friends home directory?  Should we change the permissions on this directory? 

The default job string already is +D.  And we are using that for all of our categories.  In fact, I don't think I've ever used anything but +D on any of my setups. 

We'll absolutely try adding .nzb to the file clean-up list.  But is there anything else we should worry about?

If we add .nzb files to the clean-up list, will it delete the _unpack directories that they're showing up in as well?  Or just the files within?  The directories are obviously just as much of a mess, especially when they're named using the Binsearch search field (e.g. show x264 nzb) rather than the full name with containing S01E07, etc.  So the directory structure gets pretty polluted since the TV sorting logic doesn't know where to put the first NZB (although it handles the subsequent NZBs just fine since they're named fully and comply with the proper conventions like Show.s01E07.x264.nzb).

When no files are left, the folder should be deleted too.
At least when the OS doesn't get in the way (and we made no mistakes in the code).