Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nested rars not unpacking #485

Open
1 task done
nebakanezzer opened this issue Dec 31, 2024 · 1 comment
Open
1 task done

nested rars not unpacking #485

nebakanezzer opened this issue Dec 31, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@nebakanezzer
Copy link

Is there already an issue for your problem?

  • I have checked older issues, open and closed

NZBGet Version

v24.5-stable

Platform

Linux/Docker

Environment

debian 12 vm / proxmox
unrar-free 0.1.3
7zip 22.01
not running in docker

Current Behavior

whenever a file is successfully downloaded and unpacked (but has a rar within a rar) nzbget only unpacks the first rar set, marks it as complete/successful, and never unpacks the nested rar. this causes sister applications like the arrs to mark files as problematic for issues such as "sample" (because the actual file is still in another rar), "no file eligible for import", or an actual unpacking error

Expected Behavior

nzbget unpacks additional rar files (I would assume within a limit, to avoid zipbomb type attacks)

Steps To Reproduce

find nzb file with nested rars, add to download queue

Logs

ERROR Tue Dec 31 2024 04:09:53 Unpack for -redacted- failed
ERROR Tue Dec 31 2024 04:09:53 Could not move file /home/warmachine/sda1/nzb/completed/TV-Shows/-redacted-/_unpack/-redacted- to /home/warmachine/sda1/nzb/completed/TV-Shows/-redacted-/-redacted-: Directory not empty

Extra information

it looks like from the logs it cannot move the second unpack, because it would move it into the folder containing the first unpack (which is why it is saying the folder isnt empty)

@nebakanezzer nebakanezzer added the bug Something isn't working label Dec 31, 2024
@nebakanezzer
Copy link
Author

poking around in extension manager, I discovered "extended unpack". I've enabled that and will test to see if this solves the issue.

@dnzbk dnzbk self-assigned this Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants