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!
Completed download left in _unpack_filename folder
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
shortskoolbus
- Newbie
- Posts: 3
- Joined: October 21st, 2013, 1:56 am
-
shortskoolbus
- Newbie
- Posts: 3
- Joined: October 21st, 2013, 1:56 am
Re: Completed download left in _unpack_filename folder
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
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.
In analogy to SickBeard it should wait for a end-of-job-scripts from SABnzbd to get a trigger.