blackkatt wrote:What do you mean with real?
The real message sent by your newsserver
blackkatt wrote:I don't have too many connections to server.
... so some other newsserver response (the 'real' response) is triggering that SAB message.
But wait: I had a look at the source code:
Code: Select all
logging.debug('Server login problem: %s, %s', ecode, msg)
if ecode in ('502', '481', '400') and clues_too_many(msg):
# Too many connections: remove this thread and reduce thread-setting for server
# Plan to go back to the full number after a penalty timeout
if server.active:
server.errormsg = T('Too many connections to server %s') % display_msg
logging.error(T('Too many connections to server %s'), server.id)
So: set SABnzbd's logging to +Debug, re-download, and as soon you see the error message check your sabnzbd.log for a line with "Server login problem". Post the output here.
For example
Code: Select all
2016-05-10 20:23:35,650::DEBUG::[downloader:574] Server login problem: 482, 482 Too many connections for your user (nntpswitch)
and
Code: Select all
$ cat ~/.sabnzbd/logs/sabnzbd.log | grep -i -e "too many" -e "server login problem"
2016-05-10 20:37:16,561::DEBUG::[downloader:574] Server login problem: 400, 400 dreader37.news.xs4all.nl: Too many connections from your host (max 4) - newsmaster@xs4all.nl
2016-05-10 20:37:16,561::ERROR::[downloader:580] Too many connections to server newszilla6.xs4all.nl