SABnzbd Forums

Since my last post, SAB has been behaving properly. If it does hang up again I'll be sure to send the files.

Same here... "Trying to fetch NZB from..." and no file is added. The LOG just says

2009-12-07 01:11:42,936::INFO::[rss:430] Adding hxxp://www.tvnzb.com/nzb/32712 (Top.Gear.14x04.HDTV.XviD-FoV) to queue
2009-12-07 01:11:42,937::INFO::[__init__:373] Fetching hxxp://www.tvnzb.com/nzb/32712
2009-12-07 01:11:42,977::INFO::[nzbqueue:90] Saving queue
2009-12-07 01:11:42,978::INFO::[__init__:634] Saving data for SABnzbd_nzo_vk9XXP in /home/zion2k/.sabnzbd/cache/SABnzbd_nzo_vk9XXP
2009-12-07 01:11:42,981::INFO::[__init__:634] Saving data for SABnzbd_nzo_s_5IJ0 in /home/zion2k/.sabnzbd/cache/SABnzbd_nzo_s_5IJ0
2009-12-07 01:11:43,057::INFO::[__init__:634] Saving data for queue9.sab in /home/zion2k/.sabnzbd/cache/queue9.sab

I'll try to debug it and send you the files the next days.

What the heck is hxxp://www.tvnzb.com/nzb/32712 supposed to be?
Are you sure?

Same issue, using nzbmatrix & ubuntu 9.10.

I can provide logs, let me know.

Yes I would like to have the logs.
It's the "hxxp" that I'm worried about, it should be :"http"
I need to know if SABnzbd or tvnzb makes the error.

BTW: the spaces in "http: / / aaa" (reported by JohnSCS) were just a cosmetic problem (fixed now).

I changed the http to hxxp, so it's not a clickable link... just for sure that there will be no legal issue because of a hyperlink.
Just forget the hxxp and dont worry.
I just send you my cache files... i hope they will be usefull.

That's a relief at least.

I think we got on top of this now.
The task that gets the NZB files from the site crashes when it needs
to report an error. Are you using French or Swedish in the UI?

The other problem is that the timeout for NZB fetches is too short (4 seconds)
because in another unrelated place in the code we set it to 4 seconds.
We found out that this a global setting, affecting the NZB fetcher,
so that errors with nzbmatrix occur more often (the site is a bit slow).

So, on to Beta4!

Good news. Thanks for the update. My feeds have luckily been behaving. I have seen some errors in the log about a malformed rss feed on occasion. But it seems to work itself out and I assume it is not the same issue.