Page 1 of 1

Completed download left in _unpack_filename folder

Posted: October 21st, 2013, 2:02 am
by shortskoolbus
Using SABnzbd for the first time so please bear with me here...

I just did a trial run with a download using drone and SABnzbd. Everything seemed to work fine except two things

1) the completed file was left in a folder called "_UNPACK_filename", and there was the same folder in the parent directory just called "filename"

2) The TV sort feature didn't seem to work. I had it structured as /show name/episode name S##E##.ext. But when i was notified that the download was complete, it left it in /series title/_UNPACK_filename/124lk12j4lkjsdf.ext <--- filename was a bunch of numbers/letters, and also created the other folder i mentioned.

Any ideas?

Thanks!

Re: Completed download left in _unpack_filename folder

Posted: October 21st, 2013, 3:46 am
by shortskoolbus
i guess its screwing up NZBdrone as well, since the _UNPACK_ folder is protected. It can't rename and then grab that file and move it over to the correct location even after it's finished unpacking the file.

Re: Completed download left in _unpack_filename folder

Posted: October 22nd, 2013, 5:28 am
by shypike
NZBdrone should keep its hands of folders names __unpack__xxx.
In analogy to SickBeard it should wait for a end-of-job-scripts from SABnzbd to get a trigger.