Get help, report and discuss bugs.
-
mgittelman
- Posts: 4
- Joined: 28 Dec 2017, 23:44
Post
by mgittelman » 29 Dec 2017, 00:16
Just installed 20.0-testing-r2159 on a freebsd jail. When I try to do a download, I'm getting the message "Direct unpack" failed. After it's done downloading, it tries to repair and unpack, but that also fails. Tried the same NZB on my Windows PC install and everything worked fine.
What might I be missing?
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 29 Dec 2017, 00:50
Click on the failed item in history, then on button "Log". Read the log.
-
mgittelman
- Posts: 4
- Joined: 28 Dec 2017, 23:44
Post
by mgittelman » 29 Dec 2017, 01:00
The log is where I got the Error "unpack failed."
Is there another log where I can get more info? That's all it says.
-
al3x
- Posts: 28
- Joined: 24 Aug 2017, 17:13
Post
by al3x » 29 Dec 2017, 01:36
I had that problem once I think. But it only occurred with one particular NZB download. In my case it had to do with improper permissions inside the rar archive which caused problems while unpacking.
That's because unrar by default tries to keep all permissions while unpacking. You can fix that by telling unrar to discard any permission changes:
Might help, not sure
-
mgittelman
- Posts: 4
- Joined: 28 Dec 2017, 23:44
Post
by mgittelman » 29 Dec 2017, 04:20
Thanks al3x! Unfortunately that did not seem to have any effect. Tried another NZB and that one failed as well. Any other ideas?
Also on one of them, i got the following message in the download log right after it failed:
ERROR Thu Dec 28 2017 20:30:09 Post-process-script Logger.py for POTC5-MRF failed (terminated with unknown status)
INFO Thu Dec 28 2017 20:30:09 Logger: env: python: No such file or directory
Not sure if it's relevant at all. Didn't show up for the other 2 I tried.
-
mgittelman
- Posts: 4
- Joined: 28 Dec 2017, 23:44
Post
by mgittelman » 29 Dec 2017, 07:48
Looks like downloading unrar from rarlabs and re-pointing to the new executable in settings fixed it for me.
-
al3x
- Posts: 28
- Joined: 24 Aug 2017, 17:13
Post
by al3x » 29 Dec 2017, 10:35
Hmm, strange. No idea what went wrong there, maybe a FreeBSD issue then. Glad you could fix it though
Who is online
Users browsing this forum: No registered users and 48 guests