Page 1 of 1

Too many connections; adding up the number of connections of active categories

Posted: 12 Jul 2018, 14:24
by Ariek
NZBget 20 (hardware: arch=armhf; select=auto)

When using nzbget 20 (stable release) I get these error messages:

Code: Select all

Authorization for EasyUsenet (reader.easyusenet.nl) failed: 482 Too many connections for your user.
Blocking EasyUsenet (reader.easyusenet.nl) for 10 sec
I use 2 download categories (movies and series) and both are using the same server/usenet service provider account.
Server 1, category name movies: number of connections: 12
Server 2, category name series: number of connections: 12
where 12 is the maximum number of connections of my usenet subscription plan.

When I download just one single item (i.e. a movie, using server 1, with 12 connections). I get the above error messages.

However, when using NZBget 19.1 (stable release) I don't get these error messages and downloads use all available connections of the corresponding category (here: 12).

Playing around with the number of connections i learned that NZBget 20 is adding up the number of connections of all active servers/categories (and use the same usenet server credentials).

server 1, 12 connections + server 2, 12 connections, total 24 connections: error mesages
server 1, 12 connections + server 2, 1 connections, total 13 connections: error mesages
server 1, 12 connections + server 2, 0 connections, total 12 connections: no error mesages
server 1, 11 connections + server 2, 1 connections, total 12 connections: no error mesages

NZBGet 19 stable dowloads items correctly, with 12 connections per server/category.

Re: Too many connections; adding up the number of connections of active categories

Posted: 12 Jul 2018, 14:32
by hugbug
What makes you think that there are connection settings per categories?

Connections are set per servers. All categories use the same server settings.

If you have two (active) servers on the same level then both servers are used at the same time and connections sum up. That's how nzbget works and always worked, no difference between v19 and v20.

Re: Too many connections; adding up the number of connections of active categories

Posted: 12 Jul 2018, 15:38
by Ariek
I understand your remark, so I try to describe it a bit differently.

Code: Select all

Server1.Active=yes
Server1.Host=reader.easyusenet.nl
Server1.Port=119
Server1.Username=****
Server1.Password=****
Server1.Connections=12
Category1.Name=movies
Category2.Name=series
Server2.Active=yes
Server2.Host=reader.easyusenet.nl
Server2.Port=119
Server2.Username=****
Server2.Password=****
Server2.Connections=12
These settings (nzbget.conf) do work with nzbget 19.1 but when using nzgbet 20 it produces the error message: too many connections.

IMHO, to download an item (and a category is assigned) nzbget 'looks' at the number of connections of the corresponding category.
So, to download a movie (category 1) nzbget uses the number of connections of `Server1.Connections=12`, or when downloading a series (category 2) nzbget uses `Server2.Connections=12` as the maximum number of connections.

NZBget 19.1 seems to do this flawlessly but NZBget 20 doesn't.
To download movie (or a series) NZBget 20 'looks' at the number of connections of both `Server1.Connections=12` and `Server2.Connections=12` simultaneously instead of only 'looking' for the max. number of connections per category (like NZBget 19.1). To me it seems that NZBget 20 is trying to establish 24 connections at the same time instead of the maxium number of connections per category.

Otherwise, I don't understand why NZBget 20 produces an error message and NZBget 19.1 doesn't using exactly the same settings.

Re: Too many connections; adding up the number of connections of active categories

Posted: 12 Jul 2018, 16:58
by hugbug
In config file one line is a setting (or comment). The order of lines has no meaning (except when referencing other settings like "${MainDir}/dst" but that's not the case here).

There is no relation between categories and servers.

It doesn't make sense to define two servers with exactly same settings. You should delete server2, at best do that via web-interface which takes care of deleting of all related entries from config-file.
Ariek wrote:
12 Jul 2018, 15:38
Otherwise, I don't understand why NZBget 20 produces an error message and NZBget 19.1 doesn't using exactly the same settings.
Because you changed something else, for example number of connections per server or added server2 which you didn't have in v19 or your Usenet provider changed the number of allowed connections etc.