SABnzbd Forums

I'm using NZBmatrix as my rss feed, and suddenly it no longer fetches anything, they remain in the queue until I remove them?

Please explain it better.
Are  no new NZB found?
Does "fetching" remain visible in the queue?
Are the NZB fetched, but nothing is downloaded?

Your question is in the "it doesn't work, help" category.

Sorry for being vague. Yes the fetching remains visible in the queue until I delete them. New nzb's are found but remain in the fetching state. It seems as though it stopped working after I installed the google chrome extension for Mac. I've disabled it now but the problem persists. Thanks.

Do the fetches finally end up in the history?
What happens when you restart SABnzbd?
Do you see any warnings?
Have you looked at the logging file?

The fetches don't end up in the history. I don't get any warnings either. I just restarted and it seems to be working now. Although it now seems to take longer than it used to fetch the nzb. Could this have been caused by the chrome extension?

Depend on what the "Chrome extension" does. What does it do?
Fetching NZB from sites should be independent of the browser.

One possible cause is that the site is so slow that it repeatedly doesn't answer
within the 60 second timeout.
But after a couple of minutes (about 10 I think) it should end up in History.

Hi, I popped in to the forum to see if anyone else was having this issue and it looks like they are.

I'm on 0.5.0RC3 on xubuntu.

For both nzbmatrix and tvnzbs, the queue is getting stuck on fetching... after several hours nothing changes. In the log, there are countless lines saying:
"Restarting crashed urlgrabber"

If you shutdown and restart sabnzbd, it works a charm and fetches the nzbs, but it seems like after the progy is running for a certain amount of time, the urlgrabber is dying out.

Is that something in my configuration somehow perhaps?

Thanks in advance

Please set your logging level to "debug".
Start SABnzbd from a console and let it run.
It looks like there is indeed a crash in the URL fetcher thread.
The console should show you where it crashes.
(At least when you are not downloading at the same time).
Alas, the crash info won't show up in the logging file.

The odd thing is that when the URL thread is automatically restarted
it will not resume fetching, while a full restart does.

Same issue with windows rc6 tried downgrading to rc3 and same issue still.  Haven't tried a clean install of rc3 but it was fine before this week with rc6.  I use both tvnzb and nzbsrus for feeds.  I'm going to go ahead and switch back to rc6 for now.

upgraded back to rc6. and now seems all good again.  maybe there was a solar flare?

RC6 contains some weak code that can crash when the server gives unexpected output.
This will be fixed in the final release.