0.7.0 Speed drops to 0. Also "failed login for server" error

[DoubleDroz]

Version: (Ex: 0.7.0)
OS: (OS X Lion 10.7.4)
Install-type: (OS X App)
Firewall Software: (OS X system Firewall)
Are you using IPV6? (No)
Is the issue reproducible? (yes)

Hey guys,

I recently installed 0.7.0 on both my OS X computers, and when starting downloads the speeds would be fine, then drop away to nothing within 10 seconds. I would receive a "failed login for server news.internode.on.net:119" error, which is strange because the server needs no log in. If i revert back to 0.6.15, the error doesn't occur and I get full speed downloading again.

This occurred on both systems. No settings changed between updates and reinstalls. The 0.7.0 install on one of the computers was totally fresh - no previous settings.

Hope someone can help?
Droz

[shypike]

The server needs no login, but do you still provide username and/or password in Config->Servers?
There was a recent change in SABnzbd to accommodate servers that insist on getting
an empty username/password.

[DoubleDroz]

Nope, no username or password provided there.

[shypike]

Can you try this from a Terminal window (Programs->Utilities).

Code: Select all

telnet news.internode.on.net 119

You should see the sign-on.
Then type:

Code: Select all

body one@two

You should get a message saying that the article is not available.
If you get some login question, there's an issue.

[Norbertus]

Quick tip: Check the number of CONNECTIONS that SABnzbd uses (Config->Servers: Connections). I have had this problem with servers that allowed an X number of connections, but reserved 2 for extra commands, with a time-out of a couple of seconds. This is to prevent clients from spamming, or DOS attacks. The solution is to reduce the amount of connections and increase the time-out time.

[DoubleDroz]

Shypike, the telnet command spits out

Code: Select all

Connected to news.internode.on.net.
Escape character is '^]'.
200 news.astraweb.com NNRP Service Ready (posting ok) (yEnc enabled).
body one@two
430 No such article

Norbertus, the connections are exactly the same as they always were, but I have tried different combinations and gotten the same result. I had my connections set at 8, because that's what the maximum recommended connections are from my ISP (the ISP supplies premium newsnet with the accounts! So... I get full and constant speed on 0.6.15 (which I have reverted to) and get the speed drop all the way to zero on 0.7.0.

I will try installing 0.7.0 and increasing the time-out time on one of my machines and then trying again, but I'd get that log-on message within a few seconds of trying to download files...

[shypike]

That's a perfectly normal response.
Looking at the change history of SABnzbd, there are very few changes in the download part.
In fact the only one that could be relevant is this case is the randomization of IP addresses
when a provider has multiple ones.
You could test this by going to Config->Special and set the option "random_server_ip" off.

[eggbert]

There appear to be a few of us using the same ISP (Internode in Australia) which are having the same issue.

I am using Win 7, but am having the same issue as Droz above. It should be noted that this is intermittent. Sometimes Sabnzbd will work fine, and at others the server will become "blocked" in the Warnings / Connections tab, and nothing will come down.

I also have a (limited speed) xusenet connection, but that appears to be chugging along fine. It is just the internode connection that is the issue, however it does not seem to affect all Internode users.

Droz and one other have indicated that dropping back to a previous version of Sabnzbd has worked for them. I will try this tonight, and see what happens.

[shypike]

Anyone tried to set the random_server_ip option off?

[Norbertus]

Although I cannot test with the specific server, Google shows that news.internode.on.net shows these problems for more users, using different software. news.internode.on.net is an alias for some astraweb.com servers. All IP addresses (using OpenDNS 208.67.222.222) appear to be valid and responsive, but with a short time-out after connecting (less than 4 seconds). The servers are located in the USA, so lag could be the cause of your problems. Also, they appear to be unsupported.

The Dutch provider EWEKA (paid, €1,10 for 24 hours access) offers the best connections in the Netherlands and surrounding countries. Although you're at the other end of the planet, and perhaps a paid service may be too expensive, I'd suggest trying a different provider... Here's one with a 21-day free trial: Newshosting (USA)

By the way, I'm not sure if setting the time-out to 3 seconds, but it might just work (risky!)

[eggbert]

Anyone tried to set the random_server_ip option off?

Just got home from work, and trying it now. So far it looks good, but I will see how it works over the evening.

/Edit Seems to have done the trick for me

[DoubleDroz]

Sorry for the absence, I've been busy!

Anyway, when I downloaded SAB again, I found it was 0.7.1... after installing I've had full and consistant speeds without altering any settings.

If i have a bit more time, I'll install 0.7.0 and see what happens. However, as it stands, the new release 0.7.1 has (some how?) fixed my problem. In the special settings, random_server_ip is set to "on".

I'll make sure to keep everyone informed about whether my speeds remain great!

Thanks for the help

[Norbertus]

Better to be absent than to sit behind a computer all day waiting for a download that isn't working . It appears that 0.7.1 works a whole lot better on 10.7.4 on multiple levels. As if this version was written for Lion and the other version for Snow Leopard, with Rosetta.

[DoubleDroz]

Better to be absent than to sit behind a computer all day waiting for a download that isn't working

Ain't that the truth! Still, I guess I was happy to have it working either way - 0.6.15 seemed to work fine, and I think I've lost that urge to have the newest version of everything due to having a play with linux - updates would *always* break things. And if it ain't broke - don't fix it.

...but here's to 0.7.1!