Hi!
I have been using sabnzbd for a long time without any problems. However after I updated to 0.7.14 something weird started to happen. The downloads complete (100%) then get stuck in the downloads panel. The postprocess never starts. When I restart sabnzbd, those stuck downloads no longer appear in the lists (downloads or history). This only happens for some of the downloads, not all.
I can see the __ADMIN__ directory with the files in them, but they are tiny, only ~KBs. The download panel shows (before they disappear after restart) that the entire GBs of file was downloaded completely.
Any thoughts what might be causing the issue?
Thanks in advance!
Downloads stuck at 100%, nothing happens
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- 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.
-
SloppyPenguin
- Newbie
- Posts: 2
- Joined: August 31st, 2013, 11:36 am
Re: Downloads stuck at 100%, nothing happens
Which operating system?
-
SloppyPenguin
- Newbie
- Posts: 2
- Joined: August 31st, 2013, 11:36 am
Re: Downloads stuck at 100%, nothing happens
Raspbian wheezy with Python 2.7.3shypike wrote:Which operating system?
$ uname -a
Linux rp 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l GNU/Linux
Thanks!
Re: Downloads stuck at 100%, nothing happens
Could be a problem with par2cmdline in which case it should be solved by 0.7.15.
Can you set logging level to Debug (Status page) and check the logfile
after a job hangs?
Disappeared jobs should show up in the Status->QueueRepair.
Can you set logging level to Debug (Status page) and check the logfile
after a job hangs?
Disappeared jobs should show up in the Status->QueueRepair.