Page 1 of 1
NZB hangs in history with queue status, what gives?
Posted: September 21st, 2008, 6:30 am
by Fisco
Greetings fellow forum members!
I've been using Sabnzbd for a long time now with no problems whatsoever. But since a few days i'm experiencing some strange behaviour.
Every time i add an nzb in the queue list it downloads just fine but when it is complete it just hangs in the history like....forever!
He download the files just fine, i just can't get past the queue status.
I do notice that i get different warnings saying that he can't read the NZB but i have no idea how to fix this.
This happens to all the NZB's by the way and is not limited to one.
Version: Sabnzbd version: 0.4.4
OS: Windows XP SP3
Install-type: Windows Installer, Windows zip, i tried both.
Skin: SMPL
Firewall Software: XP SP3 Firewall
Are you using IPV6? i believe i use IPV4 (please correct me if im wrong)
Is the issue reproducible? yes
Is this a known problem? Is there a way to fix it?
Thanks is advance!
Fisco
Re: NZB hangs in history with queue status, what gives?
Posted: September 21st, 2008, 7:06 am
by switch
Has this issue just started after upgrading to 0.4.4, or did it happen when using previous versions?
Re: NZB hangs in history with queue status, what gives?
Posted: September 21st, 2008, 7:34 am
by Fisco
Hi Switch, thanks for the quick reply!
I used to use 0.4.2 without any problems. But now when i try to start that version of the program, i get a 'windows error report' screen.
In other words, i can now get more done with the newest version than with this one.
I thought that maybe Sabnzbd was still running with the newest version but i did not see it running as an process.
Cheers!
Fisco
Re: NZB hangs in history with queue status, what gives?
Posted: September 21st, 2008, 7:42 am
by switch
I can't think of any solution off hand, if you send us your
logs we may be able to help more. Zip them up and send them to
[email protected] I know you say this happens for every nzb file, but send us an example one that failed just to make sure.
Re: NZB hangs in history with queue status, what gives?
Posted: September 21st, 2008, 8:29 am
by Fisco
This is very weird. As of now, i can't seem to replicate the 'cannot read NZB' error. This is with version 0.4.2 though (Which miraculously works now BTW).
Shall i still mail the logs to the address you mentioned?
I do have another question though. According to the page which list all the parts of a download i have finished all the parts upto say part 23. But when i look at my download folder, almost half of the files are not present at first. They begin appearing after they have been downloaded a long time ago.
Is this normal? If not, i believe this is the cause of the 'hanging in history with queue status' thing because Sabznbd is waiting for all the downloaded files to be present. And this can take hours if not more.
Anyhow, i hope this all makes sense to you, you have to understand english is not my first language
.
EDIT:
Mail sent
Re: NZB hangs in history with queue status, what gives?
Posted: September 21st, 2008, 1:44 pm
by shypike
The NZB file reads OK, as you found out yourself.
The logfile does not contain any useful information.
It misses the part where the would have been refused.
Let's call it a one-time incident.
They begin appearing after they have been downloaded a long time ago.
Are you using a memory cache (Config->General)?
In that case articles are saved in memory until the file is complete.
It could be that the internal administration is damaged.
How do you stop SABnzbd?
To repair, start up SABnzbd with the extra parameter --clean.
However, this will delete all files in the queue AND the history.
Re: NZB hangs in history with queue status, what gives?
Posted: September 21st, 2008, 2:04 pm
by Fisco
Hi Shypike, thanks for your reply,
The cache setting is at 0. So i assume it isn't in use?
Normally i stop Sabnzbd via the shutdown option. But since Sabnzbd was still busy with most of the files that haddn't apeared in the folder i was unable to close it that way (it hangs at 'shutting down' and doesn't continue). So i was forced to close the program via the process window.
I tried to do the repair just like you said. But now i get the following error (i guess forcing the program was not a good idea.):
Traceback (most recent call last):
File "SABnzbd.py", line 43, in
File "sabnzbd\__init__.pyo", line 37, in
File "sabnzbd\assembler.pyo", line 30, in
File "sabnzbd\interface.pyo", line 44, in
File "Cheetah\Template.pyo", line 59, in
File "Cheetah\Compiler.pyo", line 35, in
zipimport.ZipImportError: bad local file header in D:\SABnzbd-0.4.2-win32-bin\SABnzbd-0.4.2\lib\sabnzbd.zip
Traceback (most recent call last):
File "SABnzbd.py", line 43, in
File "sabnzbd\__init__.pyo", line 37, in
File "sabnzbd\assembler.pyo", line 30, in
File "sabnzbd\interface.pyo", line 44, in
File "Cheetah\Template.pyo", line 59, in
File "Cheetah\Compiler.pyo", line 35, in
zipimport.ZipImportError: bad local file header in D:\SABnzbd-0.4.2-win32-bin\SABnzbd-0.4.2\lib\sabnzbd.zip
I will try a system restart and will edit the post accordingly if that helps.
Cheers!
Fisco
EDIT:
Ok after re-unpacking the sabnzbd zip the error was gone. I did however got an notification from Windows saying that some of the hard-drive clusters where damaged. Windows then began a repair but that also did not help much.
I also cleaned the newly unzipped sabnzbd but that did not help either.
Thanks for the help so far!
Re: NZB hangs in history with queue status, what gives?
Posted: September 28th, 2008, 2:46 pm
by stomp
I am experiencing this also. For me, the problem is that SABnzbd+ tries to open a .nzb before its download completion. For large .nzb's, it can takes up to 10 seconds to download. If the folder monitoring time is smaller than the time needed to download the .nzb, SABnzbd+ will try to load it and fail as the file is not complete.
My guess...
Re: NZB hangs in history with queue status, what gives?
Posted: September 28th, 2008, 3:00 pm
by shypike
You should not be using 0.4.2, since at least 3 problems regarding the Watched folder scanner
were solved on 0.4.3 and 0.4.4.