Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
I have the following problem. I installed sabnzbd Version: 0.7.18 on my Zyxel NSA 325 with ffp depending on this tutorial: http://forum.nas-central.org/viewtopic. ... 49&t=10881
It worked well a few days. But yesterday I came home and saw that the history stuck when calling SabToSickbeard.py.
I restarted my NAS but it still doesn't continue. So i deleted the files history.db, postproc1.sab, queue9.sab in my admin folder and restarted the NAS again. So my history was cleared but it continued working with the next files. Today I had the same problem, but not with "Running script sabtosickbeard", but Starting repair.
What can be wrong? It sucks everytime delete these files and restart the nas. Is it because high utilization? How can i fix it in the future?
The par2 repair process (external utility) is notorious for needing a lot of CPU capacity and possible memory.
And extensive repair of a large download may take days on a lowly CPU.
