Page 1 of 1
SAB: "Suspected error in downloader"
Posted: January 5th, 2014, 12:56 am
by tucansam
When Type Warning
2014-01-04 22:12:22,562 ERROR: Suspect error in downloader
2014-01-04 22:12:11,733 ERROR: Suspect error in downloader
2014-01-04 22:12:05,890 ERROR: Suspect error in downloader
2014-01-04 22:11:53,608 ERROR: Suspect error in downloader
2014-01-04 22:11:46,750 ERROR: Suspect error in downloader
Windows XP, v0.7.16.... Have been seeing this in the logs a lot the last few months, last two days there are literally hundreds of these entries per day.
What could be causing it?
Re: Suspected error in downloader
Posted: January 5th, 2014, 1:07 am
by tucansam
Getting a lot of this too:
2014-01-04 19:16:04,296::INFO::[_cplogging:55] [04/Jan/2014:19:16:04] ENGINE Bus STARTING
2014-01-04 19:16:04,328::INFO::[_cplogging:55] [04/Jan/2014:19:16:04] ENGINE Started monitor thread '_TimeoutMonitor'.
2014-01-04 19:16:04,546::INFO::[_cplogging:55] [04/Jan/2014:19:16:04] ENGINE Serving on 0.0.0.0:8080
2014-01-04 19:16:04,546::INFO::[_cplogging:55] [04/Jan/2014:19:16:04] ENGINE Bus STARTED
2014-01-04 21:07:27,671::INFO::[_cplogging:55] [04/Jan/2014:21:07:27] ENGINE Bus STOPPING
2014-01-04 21:07:40,608::INFO::[_cplogging:55] [04/Jan/2014:21:07:40] ENGINE Bus STOPPING
2014-01-04 21:08:48,578::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 8080)) shut down
2014-01-04 21:08:48,608::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE Stopped thread '_TimeoutMonitor'.
2014-01-04 21:08:48,608::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE Bus STOPPED
2014-01-04 21:08:48,608::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE Bus EXITING
2014-01-04 21:08:48,608::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE Bus EXITED
2014-01-04 21:08:48,717::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 8080)) shut down
2014-01-04 21:08:48,717::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE No thread running for _TimeoutMonitor.
2014-01-04 21:08:48,717::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE Bus STOPPED
2014-01-04 21:08:48,717::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE Bus EXITING
2014-01-04 21:08:48,717::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE Bus EXITED
2014-01-04 21:08:48,717::INFO::[_cplogging:55] [04/Jan/2014:21:08:48] ENGINE Re-spawning C:\Program Files\SABnzbd\SABnzbd.exe
2014-01-04 21:38:40,030::INFO::[_cplogging:55] [04/Jan/2014:21:38:40] ENGINE Bus STARTING
2014-01-04 21:38:40,030::INFO::[_cplogging:55] [04/Jan/2014:21:38:40] ENGINE Started monitor thread '_TimeoutMonitor'.
2014-01-04 21:38:40,250::INFO::[_cplogging:55] [04/Jan/2014:21:38:40] ENGINE Serving on 0.0.0.0:8080
2014-01-04 21:38:40,250::INFO::[_cplogging:55] [04/Jan/2014:21:38:40] ENGINE Bus STARTED
2014-01-04 22:11:46,750::ERROR::[downloader:717] Suspect error in downloader
2014-01-04 22:11:53,608::ERROR::[downloader:717] Suspect error in downloader
2014-01-04 22:12:05,890::ERROR::[downloader:717] Suspect error in downloader
2014-01-04 22:12:11,733::ERROR::[downloader:717] Suspect error in downloader
2014-01-04 22:12:22,562::ERROR::[downloader:717] Suspect error in downloader
I've tried reinstalling sab.... Perhaps I should reinstall python?
Re: Suspected error in downloader
Posted: January 5th, 2014, 1:08 am
by sander
It is caused by an exception that is not caught in request_article.
You can set the logging to +Debug (in Status tab), and see what you get.
If you were on Linux, you could edit the source and add a extra logging ...
Code: Select all
def __request_article(self, nw):
try:
nzo = nw.article.nzf.nzo
if cfg.send_group() and nzo.group != nw.group:
group = nzo.group
if sabnzbd.LOG_ALL:
logging.debug('Thread %s@%s:%s: GROUP <%s>', nw.thrdnum, nw.server.host,
nw.server.port, group)
nw.send_group(group)
else:
if sabnzbd.LOG_ALL:
logging.debug('Thread %s@%s:%s: BODY %s', nw.thrdnum, nw.server.host,
nw.server.port, nw.article.article)
nw.body(nzo.precheck)
fileno = nw.nntp.sock.fileno()
if fileno not in self.read_fds:
self.read_fds[fileno] = nw
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('Suspect error in downloader')
logging.info("Traceback: ", exc_info = True)
self.__reset_nw(nw, "server broke off connection", quit=False)
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 4:51 am
by Shangjulz
Nice, but how do I get into the source file to add the extra logging
and where exactly should I enter it into?
I hope you are in today Sander, I really need your help here
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 5:07 am
by sander
You're replying to a post that's more than 2 years old?
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 5:31 am
by Shangjulz
Yes...newbie
new to Linux
SABnzb
news.servers
etc...
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 5:45 am
by sander
Start by filling this out:
SABnzbd Version:
OS:
Install-type:
Is the issue reproducible?
SABnzbd logging:
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 6:15 am
by Shangjulz
OK thanx
Start by filling this out:
SABnzbd Version: -- 1.0.0RC1 [00de72b]
OS: -- Ubuntu Freya
Install-type: -- Python Version:2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2]
Is the issue reproducible? -- it happens a few times, 1 out of 5 I would say
SABnzbd logging: -- sorry, I do not know what this means
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 6:22 am
by sander
Shangjulz wrote:
SABnzbd logging: -- sorry, I do not know what this means
Post the error, and the relevant lines from the file sabnzbd.log
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 9:29 am
by Shangjulz
Hee-hee,
Thank you !
2016-02-24 12:26:35,978::INFO::[decoder:226] <Article: article=************@EC3******3.newsup, bytes=768000, partnum=73, art_id=None> => missing from all servers, discarding
2016-02-24 12:26:36,404::INFO::[downloader:661] Thread
[email protected]: Article *******************@EC3********.newsup missing (error=430)
I got a new news server (newshosting), maybe that will work..
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 9:34 am
by Shangjulz
OK this makes no sence, I can not find this episode on 3 servers but streaming on Kodi works?
log from terminal on NEW server
2016-02-24 16:32:54,455::INFO::[downloader:661] Thread
[email protected]: Article
[email protected] missing (error=430)
2016-02-24 16:32:54,457::INFO::[downloader:661] Thread
[email protected]: Article
[email protected] missing (error=430)
2016-02-24 16:32:54,459::INFO::[downloader:661] Thread
[email protected]: Article
[email protected] missing (error=430)
2016-02-24 16:32:54,461::INFO::[downloader:661] Thread
[email protected]: Article
[email protected] missing (error=430)
2016-02-24 16:32:54,462::INFO::[downloader:661] Thread
[email protected]: Article
[email protected] missing (error=430)
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 9:39 am
by shypike
Streaming on Kodi, from what source? A torrent?
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 9:44 am
by sander
What does your logging have to with "Suspected error in downloader", the title and subject of this thread?
I have the idea you're posting into a random, non-related forum thread. I find that confusing and annoying. Please start your own thread.
HTH
Re: SAB: "Suspected error in downloader"
Posted: February 24th, 2016, 9:51 am
by Shangjulz
Suspect error in downloader was the print out on the GUI on SAB
Kodi stream from Exodus, with realdebrid
But thannx for looking into this anyway.
I changed alot of settings and since the SSL were disabled the download error seems to be gone for the last 30 min or so, authentication issues now.
+1 to sander for leading me into the right direction!