"Suspect error in downloader"

[apcrcom]

Version: 1.0.0
OS: W7x64
Install-type: Windows Installer
Skin (if applicable): Glitter
Firewall Software: Windows
Are you using IPV6? No
Is the issue reproducible? Yes

I upgraded to 1.0.0 a few days ago

SABNZBD keeps reporting the error "Suspect error in downloader"

I pulled the log from /users/x/appdata/local/sabnzbd/logs but it only has info to the 20th of this month, today being the 23rd. Errors are constant and so nothing for last 3 days. (Attribute for the file is also 20th)

Settings for log location look correct .. http://prntscr.com/ainydf

Can anyone help with this error?

Thanks

Jim

[sander]

Hi,

That message is printed by the last & unspecified except in this piece of SABnzbd source code:

Code: Select all

def __request_article(self, nw):
        try:
<snip>
        except socket.error, err:
            logging.info('Looks like server closed connection: %s', err)
            self.__reset_nw(nw, "server broke off connection", quit=False)
        except:
            logging.error(T('Suspect error in downloader'))
            logging.info("Traceback: ", exc_info=True)
            self.__reset_nw(nw, "server broke off connection", quit=False)

So ... something went wrong in getting the article from the newsserver.

The interesting is in the part what SABnzbd prints right before and in the "Traceback:". As you can't find the logging, and would do this:
1) stop SABnzbd
2) open CMD.exe
3) go to the directory containing sabnzbd.exe and sabnzbd-consolese.exe
4) in that directory start sabnzbd-CONSOLE.exe

As soon as the problem occurs, you should see the Traceback info, which will tell the cause.

[apcrcom]

Thanks

Just a quick question,

I have started sabnzbd-CONSOLE.exe

The "traceback info" - will this be in the CMD window, or in the log file, or in some other location?

Just wondering where I should look to find it.

Thanks

Jim

[sander]

in the CMD window.

(Well, also in the log file, but you can't find that ...)

[apcrcom]

This is what its saying concurrent with the error report on the main interface (9.05am)

http://prntscr.com/aipklf

[sander]

OK. "Good" ... ;-)

Can you copy-paste the lines around the Tracekback and paste them here? Makes it easier for reading and searching.

It's about:

Code: Select all

syscall error 10053 "software caused connection abort"

When you Google that, you find all kinds of possible remedies. I'll leave that to you ...

In your case I would start by lowering the number of newsserver connections, for example 6, and then try again.

Oh, and this:
- any special setup stuff you want to tell about? Proxy? Virtual Machine? ... ? ... ?
- is that really Windows 7? I'm no Windows expert, but that interface (bottom bar) looks a bit old fashioned?

[apcrcom]

Thanks!

I switched connections to '6'. Will post back result.

No proxys. Its just a headless windows box but viewed through VNC

The OS is W7x64. I just turn off all the visual effects and wallpapers and stuff coz not required on a server.

J

[sander]

Can you post an update? Did the workaround work?

Can you post the traceback error message: from the sabnzbd-console.exe output or from logging:

There is a way to always find your sabnzbd.log file: in SAB 1.0.0 with Glitter interface, in the upper right corner click on "Status and Interface Options" (the wrench symbol). In the popup, in the lower left corner, click on "Show Logging". That will download the logging.