I'm getting these errors on almost all my nbzmatrix URLs.
2010-05-05 21:05:46,875 ERROR: Error getting url http://nzbmatrix.com/api-nzb-download.p ... rname=blah &apikey=blahblah (cause= "Invalid nzbmatrix report number 555555")
The console will repeat "Restarting crashed urlgrabber"
If I put the URL into my web browser it will download the nzb just fine. If I manually add the downloaded nzb file to sabnzbd it will work fine. Anyone else having this issue? Any ideas on what the issue might be?
Version: 0.5.2
OS: Windows 2003 ENT
Install-type: Windows Installer
Skin (if applicable): Smpl-Black
Firewall Software: None
Are you using IPV6? No
Is the issue reproducible? Yes
nbzmatrix URL issues?
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.
Re: nbzmatrix URL issues?
We've had some more complaints about this.
The problem is that so far we cannot reproduce the problem at all.
This suggests that there's some error in SABnzbd that is triggered
by occasional peculiar behaviour of nzbmatrix or possibly specific
characteristics of the system SABnzbd runs on.
The message "Invalid nzbmatrix report number 555555" will only be given when
nzbmatrix send garbage instead of an NZB file (usually an HTML page).
Does the problem ever repair itself?
The crash should repair itself, although if it crashed due to a persistent
condition, it will keep crashing without getting anywhere.
The problem is that so far we cannot reproduce the problem at all.
This suggests that there's some error in SABnzbd that is triggered
by occasional peculiar behaviour of nzbmatrix or possibly specific
characteristics of the system SABnzbd runs on.
The message "Invalid nzbmatrix report number 555555" will only be given when
nzbmatrix send garbage instead of an NZB file (usually an HTML page).
Does the problem ever repair itself?
The crash should repair itself, although if it crashed due to a persistent
condition, it will keep crashing without getting anywhere.
Re: nbzmatrix URL issues?
The problem does not repair itself. I've tried restarting SABnzbd and it doesn't help. I've tried deleting and adding the URL from the queue and that does not resolve the issue.
If I come up with any more information I will let you know. Thanks!
If I come up with any more information I will let you know. Thanks!
Re: nbzmatrix URL issues?
So far I have discovered a bug in the creation of a retry link for the History page.
This happens only when SABnzbd decides it's a persistent error and only
when you have set an explicit post-processing value in the RSS-feeds or the categories.
This will be fixed in 0.5.3 along with some more persistence in retries.
Now SABnzbd can be too quick in deciding that it's a hopeless case.
This happens only when SABnzbd decides it's a persistent error and only
when you have set an explicit post-processing value in the RSS-feeds or the categories.
This will be fixed in 0.5.3 along with some more persistence in retries.
Now SABnzbd can be too quick in deciding that it's a hopeless case.
Re: nbzmatrix URL issues?
I have the same issue. It used to work fine, then it seemed to stop. Occassionally a download gets through - just today I had 8 items in the queue all saying "Trying to fetch NZB from", when I restarted sabnzbd the last one in the queue started downloading, but the rest didn't.
I just tried an experiment and might have fixed it. Some of the URL's in my sabnzbd queue were now invalid. It seems like once it fails trying to fetch a URL, it doesn't try to fetch any others in the queue and keeps saying "Restarting crashed urlgrabber". I deleted everything from the queue and started fresh, did a quick test, appears to be working.
Version: 0.5.2 - smpl Version: 1.3
OS: Win 7
Install-type: Windows Installer
Skin (if applicable): Default - smpl-white
Firewall Software: Win 7 Firewall
Are you using IPV6? no
Is the issue reproducible? yes
I just tried an experiment and might have fixed it. Some of the URL's in my sabnzbd queue were now invalid. It seems like once it fails trying to fetch a URL, it doesn't try to fetch any others in the queue and keeps saying "Restarting crashed urlgrabber". I deleted everything from the queue and started fresh, did a quick test, appears to be working.
Version: 0.5.2 - smpl Version: 1.3
OS: Win 7
Install-type: Windows Installer
Skin (if applicable): Default - smpl-white
Firewall Software: Win 7 Firewall
Are you using IPV6? no
Is the issue reproducible? yes
Re: nbzmatrix URL issues?
I have the same problem, but one thing is I'm using the API plus Sick Beard - perhaps that's somehow triggering a bug in SABNZBD+? Though I still have 0.5.0 . . .
Re: nbzmatrix URL issues?
You should upgrade to 05.3RC1.jp10558 wrote: Though I still have 0.5.0 . . .
Several nzbmatrix related problems were solved.
Re: nbzmatrix URL issues?
I was using sickbeard too.jp10558 wrote: I have the same problem, but one thing is I'm using the API plus Sick Beard - perhaps that's somehow triggering a bug in SABNZBD+? Though I still have 0.5.0 . . .
-
- Newbie
- Posts: 1
- Joined: November 9th, 2010, 10:05 am
Re: nbzmatrix URL issues?
I had this same issue when using SickBeard and any version of SabNZBD (0.5.5 currently). I would get the "invalid nzbmatrix report number" error, but if I copy and pasted the URL to my browser, it would pop up with the NZB file to download.
The issue for me was in Sickbeard->Config->Search Providers.
There was a after my username, so it would include that space character in the URL. Something that SABNZBD does not like, but my browser was able to still interpret. Check both your API key and username for a space just before or after it.
Also, you can look in the SABNZBD error log and see if there is a space in the URL.
The issue for me was in Sickbeard->Config->Search Providers.
There was a after my username, so it would include that space character in the URL. Something that SABNZBD does not like, but my browser was able to still interpret. Check both your API key and username for a space just before or after it.
Also, you can look in the SABNZBD error log and see if there is a space in the URL.