kloaknet wrote:Thanks for reporting this feature, I would expect that it is related to the setting scriptPauseQueue setting, but you thought about that already . But there are 2 other options that might be related: UnpackPauseQueue and ParPauseQueue, and i think those also need to be set to No.garyleecn wrote:just add this to my setup (nzbget 17.1 on Synology),
and I realize a problem.
when there's a queue in my NZBGet,
it will download the first in the queue (of course), then this task will stuck at "PP-QUEUED" status, until the 2nd task finishes downloading. at which point NZBGet will start post-process (repair, unpack, run PPscripts) on the first task, and start downloading 3rd task. but now the 2nd task will again stuck at "PP-QUEUED" until the 3rd finishes downloading, so on and so forth.
my setup was running smoothly for more than a year, and the only thing I did is adding completion.py as "scan script" and "queue script", the setting in completion.py is untouched as default, and scriptPauseQueus is set to NO.
so any idea on how should I fix this?
I haven't notice the issue (4 cores, 3 for unpack, all above 3 settings on NO), but I think it happens because:
- when a complete download is finished,
- no other items are downloading,
- the script gets the first position in the PP-queue list, (par check, unpack and scripts),
- the script goes full throttle for the next NZB to check as first item in the PP-queue,
- unpauses an nzb
- and NZBget thinks, lets download instead of doing some PP-ing like unpack.
But I am not 100% sure, please provide some logs without the above 2 options on your values, some logs with the 2 options above on No.
How many cores does your NAS have?
If that doesnt help, we may need hugbug, as I can't see an option to prioritize unpacking or use an NZBNA_EVENT that triggers after the PP-scripts are done. I start my script on these options:The issue probably is related to the last section on this page: https://github.com/nzbget/nzbget/wiki/Queue-scripts
Code: Select all
event = os.environ['NZBNA_EVENT'] if (event == 'NZB_ADDED' or event == 'NZB_DOWNLOADED' or event == 'NZB_DELETED' or event == 'NZB_MARKED'):
Important side note, if you don't let the script also run as a scheduler script'(NZBget versions below 18), it could worse the'availability due to possible take downs. If the nzb is not there yet while it is propagating, the script checks it, and notices it is not ~90% there, and leaves the nzb paused. If now no other nzbs are added for say 8 hours, the nzb would NOT be checked again in this time window, and it could easily be taken down in the 8 hour time window. The scheduler part is of real importance to have the script working for propagation issues!
oddly enough, it kinda fixed itself...
what I did is, remove completion script from queue/scan scripts (btw, this is the only script I use, besides another PP script for some certain categories), reload the NZBGet, then add them back, reload NZBGet again, now it is working just fine...
btw, is it possible to have it ignore the age, just move from top to bottom of the queue?