Page 1 of 1

Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: April 22nd, 2018, 5:39 pm
by PiERiT
Not sure when but Direct Unpack stopped working at some point in my install of SABnzbd (2.3.2). I went back about 20 history pages and none of them say they were Direct Unpacked. I confirmed the setting is enabled and my temp drive is an SSD with write speeds well over the requirement.

Not a whole lot in the log but this appears for each download:

INFO::[directunpacker:372] Aborting DirectUnpack for None

Edit: Updated to 2.3.3, same problem. I then downgraded to 2.3.0 and it works again. So I'll stick with that for now.

Edit2: This ended up being due to my indexer inserting a single fake article into NZBs for tracking purposes. Safihre was very helpful and helped me to setup the developer version of SAB and remove the missing article check in the direct unpack function to get it working in my scenario.

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: April 23rd, 2018, 12:54 am
by safihre
You shouldn't be on 2.3.0, it has a number of bugs.

Maybe you can enable +Debug logging (on 2.3.3) in the Status and Interface settings window and then download something again that should Direct Unpack. Then send me the log (click Show Logging) at [email protected]

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: April 23rd, 2018, 7:13 am
by PiERiT
Sure, I will do that later today.

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: April 23rd, 2018, 7:02 pm
by PiERiT
Sent. Thank you.

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: April 24th, 2018, 2:35 am
by safihre
In this case the problem was:

Code: Select all

2018-04-23 18:52:22,948::DEBUG::[nzbstuff:1435] Download Quality: bad-articles=1
When we detect missing articles, we don't start Direct Unpack since we can be 99% sure it will fail.

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: April 24th, 2018, 7:44 am
by PiERiT
Is that a change since 2.3.0? That same download direct unpacked in that version. 99% of my downloads direct unpack on 2.3.0, whereas 0% do on 2.3.2 and later.

I noted in the History tab that every download states "1 articles was missing", regardless of version.

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: April 24th, 2018, 12:45 pm
by safihre
Maybe you can send me some example NZBs?
It's a bit strange, should only Abort after 5 bad articles.

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: April 24th, 2018, 7:47 pm
by PiERiT
I will send you the one I've been testing with. It always direct unpacks in 2.3.0 and never does in 2.3.3.

Thanks for the help. Very strange indeed.

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: June 2nd, 2018, 11:18 pm
by bobffs2
I have the same issue too with my indexer injecting a single fake article that causes direct unpack not to start. Can you tell me how to remove the missing article check? Thanks!

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: June 3rd, 2018, 2:41 am
by safihre
What OS are you on?

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: June 3rd, 2018, 10:58 am
by bobffs2
Windows 10 64-bit

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: June 3rd, 2018, 6:33 pm
by PiERiT
bobffs2 wrote: June 2nd, 2018, 11:18 pm I have the same issue too with my indexer injecting a single fake article that causes direct unpack not to start. Can you tell me how to remove the missing article check? Thanks!
Start with this: https://sabnzbd.org/wiki/installation/i ... ce-windows

The rest of this isn't exact, but when that's done, go to %userprofile%\sabnzbd (or wherever you installed to), then another folder called sabnzbd, then edit the directunpacker.py file. I don't have the original file anymore, so I don't recall precisely what it said, but in the check_requirements section, there's something like 'self.nzo.missing.articles' that you want to remove whilst leaving the other checks. So my line now reads:

if not cfg.direct_unpack() or self.killed or not self.nzo.unpack or sabnzbd.newsunpack.RAR_PROBLEM:

After that edit, save the file and compile it -- from command prompt run 'python %userprofile%\sabnzbd\sabnzbd\directunpacker.py'.

Hope that helps.

Re: Direct Unpack Not Working "Aborting DirectUnpack for None"

Posted: June 9th, 2018, 12:21 pm
by bobffs2
Thank you, that worked!