SABnzbd Forums

Never seen this before.  havent changed a thing so no idea what it'd be from.


EX:  "fetching msgid 5221219 from www.newzbin.com"  Just sticks in the queue but never actually fetches.  Just stays there.  Had a warning yesterday that "newzbin changed its protocol."

Any idea  how to get it to fetch properly would be much appreciated. 

Possible due to a (temporary) problem with newzbin.
What happens if you delete the job and re-enter the report number?

Can anyone confirm having this atm? I've added the job this morning and now it's still fetching with the above error. Might be that newzbin is messing up, but I would like that confirmed by someone else here.

yes 14779days

Look at this topic: http://forums.sabnzbd.org/index.php?topic=4376.15 It's a newzbin issue.

It was working earlier today, but now in my logfile I get the following messages:

2010-06-20 23:51:58,875::INFO::[newzbin:231] Fetching NZB for Newzbin report #
2010-06-20 23:52:01,344::INFO::[newzbin:298] Newzbin says we should wait for 52 sec
2010-06-20 23:53:02,359::INFO::[newzbin:231] Fetching NZB for Newzbin report #
2010-06-20 23:53:07,089::INFO::[newzbin:298] Newzbin says we should wait for 58 sec
2010-06-20 23:54:14,415::INFO::[newzbin:231] Fetching NZB for Newzbin report #
2010-06-20 23:54:18,703::INFO::[newzbin:298] Newzbin says we should wait for 48 sec
2010-06-20 23:55:15,511::INFO::[newzbin:231] Fetching NZB for Newzbin report #
2010-06-20 23:55:18,020::INFO::[newzbin:298] Newzbin says we should wait for 60 sec
2010-06-20 23:56:27,451::INFO::[newzbin:231] Fetching NZB for Newzbin report #
2010-06-20 23:56:29,320::INFO::[newzbin:298] Newzbin says we should wait for 53 sec

That's the newzbin rate-limiting that kicks in.
SABnzbd was working perfectly with the old newzbin.
We're not prepared to spend time on newzbin2 support until they are stabilized.
They claim compatibility with the old newzbin, so it's up to them to keep their promise.