I'm using SickBeard which is a tool for finding certain content on Usenet and then sending NZB URLs to SABnzbd for it to download and it worked great until I recently upgraded SickBeard.
SABnzbd has this in the queue:
Trying to fetch NZB from http://nzbmatrix.com/api-nzb-download.p ... pikey=xxxx
...but in the log it shows a bunch (10 or more) of these:
2010-06-11 07:30:04,716::INFO::[__init__:751] Restarting crashed urlgrabber
I've deleted my SABnzbd cache and it worked for about a day but now the problem is back again.
Can anybody tell me how to fix this?
Restarting crashed urlgrabber?
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.
Restarting crashed urlgrabber?
Last edited by sofakng on June 11th, 2010, 7:20 am, edited 1 time in total.
Re: Restarting crashed urlgrabber?
Mentioning which SABnzbd release you use would be helpful.
Re: Restarting crashed urlgrabber?
Sorry! I could've sworn I mentioned it but it looks like I didn't... (doh!)
I'm running 0.5.2.
I've noticed that SickBeard was putting a space in the URL which I'm betting was the problem. I've restarting SABnzbd, fixed SickBeard, and so far it's working... I'll post back if it continues to give me a problem...
I'm running 0.5.2.
I've noticed that SickBeard was putting a space in the URL which I'm betting was the problem. I've restarting SABnzbd, fixed SickBeard, and so far it's working... I'll post back if it continues to give me a problem...
Re: Restarting crashed urlgrabber?
Try 0.5.3RC1, it solves a couple of URL fetch issues.

