WARNING [newzbin] Problem accessing Newzbin server, wait 5 min.

[meekell]

I'm running 0.4 beta 2. I've been receiving the subject message for the last few days. I think it may have been triggered in my efforts to set up my bookmarks rss feed, which by the way doesn't work in sabnzbd. I use sabtab in firefox to add to queue, but the sab doesn't effort resolve the message id so they don't download. I've cleared the queue, restarted sab, with no luck. Any ideas?

[shypike]

Newzbin Bookmark RSS is a non-compliant RSS feed that cannot be handled by SABnzbd, don't try it.

Try to get a new RSS Search URL from the newzbin website.
The authentication string sometimes expires.

[meekell]

I did get a new url. However, this doesn't resolve the issue with fetching the nzb's by message id, does it? That's the problem I'm concerned with. The subject message is occurring when I try to add a newzbin message id. Until recently, there was no problem with the feature.

[shypike]

Are you using www.newzbin.com or v3.newzbin.com ?
If you mix them, please make sure the passwords are identical.
SABnzbd supports only v3.newzbin.com.

If you keep stuck, submit a ticket at newzbin.com, maybe there is something
wrong with your account. (This happens sometimes).
Tell them you cannot use the DirectNZB function.

[shypike]

The "wait 5 min." thing happened to me recently. I had to delete all the NZBs in the queue and re-add them for it to work. I wish the nzbs would not get stuck at "fetching msgid..." as they currently do.

Currently, any save in Config or a restart of SABnzbd will loose the internal newzbin queue, but the entries will still be in the visible queue.
I'm working on saving the msgid queue and the URL queue to disk.
Failed fetches will still remain in the visible queue (with an error message), so you can see what's happened.

[kiwi]

Well I am pleased to announce that I had the exact same problem.  I fixed it by installing Python 2.5.2 up from Python 2.4..  As well as fresh Cheetah 2.0.1 and yenc 0.3 ..  So I'm assuming it is an incompatibility with 2.4 since I had recently installed all those modules earlier trying to fix things.

Hope that helps !

[shypike]

On paper will still support Python 2.4, because some Linux distributions are very slow in picking up more recent versions.
In practice, it's just too much of a burden to actually test properly with Python 2.4
I do some superficial testing, but nothing more.

We should do more, because on smaller systems (read NAS), Python 2.5 presents some issues.