SABnzbd Forums

I have been using SABNZBd for several years and never had any problems. About two weeks ago I started seeing issues with my postprocessing and I suspect there is a ghost job in a queue and I cannot find out how to clear it. If I send a new job (nzb) to SAB it seems to create the job fine, downloads fine, extracts the files fine as well. But then the logs show that it is attempting to also unzip about 20 zip files from several weeks ago, it cannot find this files and they fail. The additional time that it adds is mildly annoying, but it fails to clean up the temp directory and run the cleanup list and that is making things messy. I have attempted purging and repairing the queue, but this still seem to come up.

Am I on the right track that it is a queue issue? Is there anything I can do to reset it?

Partial logs of last attempt:
----showing the actual file get unrared-------
2016-06-25 11:24:43,470::INFO::[postproc:353] Running unpack_magic on .....
2016-06-25 11:24:43,470::INFO::[newsunpack:229] Unrar starting on D:\Temp\CURREN~1\..........
2016-06-25 11:24:43,470::INFO::[newsunpack:450] Extracting rarfile D:\Temp\CURREN~1\...... (belonging to ......) to D:\Temp\....
2016-06-25 11:24:44,168::INFO::[newsunpack:784] Unpacked 1 files/folders in 0 seconds
2016-06-25 11:24:44,184::INFO::[newsunpack:233] Unrar finished on D:\Temp\CURREN~1\........

------------nothing else in queue and it starts trying to unzip several files-------------
2016-06-25 11:24:48,802::INFO::[newsunpack:803] Starting extract on zipfile: D:\Temp\.............
2016-06-25 11:26:02,115::INFO::[newsunpack:243] Unzip finished on D:\Temp\CURREN~1\.....
2016-06-25 11:26:02,115::INFO::[postproc:358] unpack_magic finished on ........\__ADMIN__
2016-06-25 11:26:02,302::INFO::[postproc:83] Saving postproc queue
2016-06-25 11:26:02,302::INFO::[__init__:941] Saving data for postproc2.sab in C:\Users\.............\AppData\Local\sabnzbd\admin\postproc2.sab
2016-06-25 11:26:02,302::INFO::[downloader:277] Post-processing finished, resuming download
2016-06-25 11:26:03,309::INFO::[nzbqueue:250] Saving queue
2016-06-25 11:26:03,309::INFO::[__init__:941] Saving data for queue10.sab in C:\Users\.............\AppData\Local\sabnzbd\admin\queue10.sab
2016-06-25 11:26:03,309::INFO::[__init__:941] Saving data for totals10.sab in C:\Users\.............\AppData\Local\sabnzbd\admin\totals10.sab
2016-06-25 11:26:03,309::INFO::[__init__:941] Saving data for rss_data.sab in C:\Users\.............\AppData\Local\sabnzbd\admin\rss_data.sab
2016-06-25 11:26:03,355::INFO::[__init__:941] Saving data for watched_data2.sab in C:\Users\.............\AppData\Local\sabnzbd\admin\watched_data2.sab
2016-06-25 11:26:03,355::INFO::[postproc:83] Saving postproc queue
2016-06-25 11:26:03,355::INFO::[__init__:941] Saving data for postproc2.sab in C:\Users\.............\AppData\Local\sabnzbd\admin\postproc2.sab
2016-06-25 11:26:03,355::INFO::[postproc:680] Queue has finished, launching: None (None)

One additional thing. The zip files that it is trying to extract at this point were original embedded in another .rar file.

Do you download eveything in the same folder?
If so, residual archive files can mess things up.
Inspect your final destination folder.

All of my files go to a temporary folder initially:
D:\Temp\Current Download

But under that folder they should have individual folders for each nzb that comes down. Either way, the temporary folder has been purged as well.

I was talking about your final destination folder.
If you send all files to the same folder, there's a chance this may happen.

This is resolved now. It was not going to the same destination folder, but the problem files were in a subfolder to the destination folders that were showing errors. I was able to completely remove the directory that the problem files were in and attempts to unzip have stopped now.

Thanks for pointing me in the right direction.