1.1.1 [33a7874] Win10x64 Intermittant Crash

Report & discuss bugs found in SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
mastyman
Jr. Member
Jr. Member
Posts: 57
Joined: February 27th, 2012, 9:57 pm

1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by mastyman »

Hi

second time in last few weeks, sab has crashed, saw the sab icon in tray was green, went to check what was downloading, get the following loading the webui

Code: Select all

500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last):
  File "cherrypy\_cprequest.pyo", line 670, in respond
  File "cherrypy\lib\encoding.pyo", line 220, in __call__
  File "cherrypy\_cpdispatch.pyo", line 60, in __call__
  File "sabnzbd\interface.pyo", line 407, in index
  File "_SABnzbd_interfaces_Glitter_templates_main_tmpl.py", line 526, in respond
  File "Cheetah\DummyTransaction.pyo", line 57, in getvalue
MemoryError
i have saved the logs from the crash if wanted i can pm a link.
Slate
Newbie
Newbie
Posts: 4
Joined: November 19th, 2016, 2:36 pm

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by Slate »

Same crash for me, on Win10x64 too.

Code: Select all

500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last):
  File "cherrypy\_cprequest.pyo", line 670, in respond
  File "cherrypy\lib\encoding.pyo", line 220, in __call__
  File "cherrypy\_cpdispatch.pyo", line 60, in __call__
  File "sabnzbd\interface.pyo", line 407, in index
  File "_Program_Files__x86__SABnzbd_interfaces_Glitter_templates_main_tmpl.py", line 526, in respond
  File "Cheetah\DummyTransaction.pyo", line 57, in getvalue
MemoryError
User avatar
safihre
Administrator
Administrator
Posts: 5366
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by safihre »

What did you set for Article cache?
What is sabnzbd memory usage?
Do you run sabnzbd as a service?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
mastyman
Jr. Member
Jr. Member
Posts: 57
Joined: February 27th, 2012, 9:57 pm

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by mastyman »

Article Cache is 1GB (system memory as 32GB)
didnt take a note at the time how much memory was been used at crash
Service - no. runs via startup folder.

looking at my history, last time i had this exact same error, was 24th October. so its very intermittent.
User avatar
safihre
Administrator
Administrator
Posts: 5366
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by safihre »

Maybe reduce it to 500M, this should be enough!
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Slate
Newbie
Newbie
Posts: 4
Joined: November 19th, 2016, 2:36 pm

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by Slate »

Prior to this crash, i get lots of errors about it not being able to start new threads

This is in the log, repeated many times:

Code: Select all

2016-11-19 18:38:33,470::ERROR::[downloader:448] Failed to initialize [email protected] with reason: can't start new thread
2016-11-19 18:38:33,470::INFO::[downloader:732] Thread [email protected]: failed to initialize
2016-11-19 18:38:34,421::INFO::[decoder:167] Unknown Error while decoding [email protected]
2016-11-19 18:38:34,421::INFO::[decoder:168] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\decoder.pyo", line 108, in run
  File "sabnzbd\decoder.pyo", line 282, in decode
MemoryError
My article cache limit is 450M
Not ran as a service, in startup
Cant tell exactly, but at the crash looked like memory usage decreased by around 500Mb, and total usage was 3.5Gbb. Total system memory is 16Gb

Should note that my crashes are much more frequent that mastyman, mine are multiple times per day
User avatar
safihre
Administrator
Administrator
Posts: 5366
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by safihre »

And this didn't happen with 1.1.0 or older?
MemoryError is out of Sabnzbd control, it's when the operating system doesn't allow the allocation of any memory anymore. But usually it should allow easily up to 4GB (max I ever tested).
Could you maybe try to disable virus scanner? I heard this also effects Sab from other users and gives this error types.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
mastyman
Jr. Member
Jr. Member
Posts: 57
Joined: February 27th, 2012, 9:57 pm

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by mastyman »

this never happened on the old versions no, just since last beta i believe and this release.

the only virus scanner i have running is windows defender for me.
User avatar
safihre
Administrator
Administrator
Posts: 5366
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by safihre »

Do you have multicore par2 disabled? Could this habe been during repair?
There is almost no changes between the 2 versions that could effect this.. Not that I can find at least :/
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
mastyman
Jr. Member
Jr. Member
Posts: 57
Joined: February 27th, 2012, 9:57 pm

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by mastyman »

its possible i might have skipped a couple beta releases this time around, perhaps the one from october was 2+ beta releases behind

i have multicore par2 enabled.
mastyman
Jr. Member
Jr. Member
Posts: 57
Joined: February 27th, 2012, 9:57 pm

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by mastyman »

theres literally thousands of these in the log not long before the crash btw.

Code: Select all

 
2016-11-20 07:42:28,063::INFO::[downloader:445] [email protected]: Initiating connection
2016-11-20 07:42:28,063::ERROR::[downloader:448] Failed to initialize [email protected] with reason: can't start new thread
2016-11-20 07:42:28,063::INFO::[downloader:732] Thread [email protected]: failed to initialize
2016-11-20 07:42:31,125::INFO::[downloader:445] [email protected]: Initiating connection
2016-11-20 07:42:31,125::ERROR::[downloader:448] Failed to initialize [email protected] with reason: can't start new thread
2016-11-20 07:42:31,125::INFO::[downloader:732] Thread [email protected]: failed to initialize
2016-11-20 07:42:33,142::INFO::[downloader:445] [email protected]: Initiating connection
2016-11-20 07:42:33,142::ERROR::[downloader:448] Failed to initialize [email protected] with reason: can't start new thread
2016-11-20 07:42:33,142::INFO::[downloader:732] Thread [email protected]: failed to initialize
2016-11-20 07:42:36,206::INFO::[downloader:445] [email protected]: Initiating connection
2016-11-20 07:42:36,206::ERROR::[downloader:448] Failed to initialize [email protected] with reason: can't start new thread
2016-11-20 07:42:36,206::INFO::[downloader:732] Thread [email protected]: failed to initialize
2016-11-20 07:42:38,242::INFO::[downloader:445] [email protected]: Initiating connection
2016-11-20 07:42:38,243::ERROR::[downloader:448] Failed to initialize [email protected] with reason: can't start new thread
2016-11-20 07:42:38,244::INFO::[downloader:732] Thread [email protected]: failed to initialize
2016-11-20 07:42:38,244::INFO::[downloader:445] [email protected]: Initiating connection
2016-11-20 07:42:38,246::ERROR::[downloader:448] Failed to initialize [email protected] with reason: can't start new thread
2016-11-20 07:42:38,246::INFO::[downloader:732] Thread [email protected]: failed to initialize
User avatar
safihre
Administrator
Administrator
Posts: 5366
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by safihre »

Do you already have logging set to Debug (in the Status window)?
If so: could you send me the logs before and with the crash to [email protected]?
If not can you set it to Debug and then send me the logs when it happens again?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
mastyman
Jr. Member
Jr. Member
Posts: 57
Joined: February 27th, 2012, 9:57 pm

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by mastyman »

yep i keep it on Debug, emailed.
User avatar
sander
Release Testers
Release Testers
Posts: 8829
Joined: January 22nd, 2008, 2:22 pm

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by sander »

"can't start new thread" is a python error message. See http://stackoverflow.com/a/1835043

So: too many threads already started.

And that is consistent with the memory problem.

But: where do the threads come from ... ? Interesting ...
User avatar
safihre
Administrator
Administrator
Posts: 5366
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 1.1.1 [33a7874] Win10x64 Intermittant Crash

Post by safihre »

New threads are started for example when the main server doesn't have the article and SAB will try to connect to the next-priority server to try and see if that one has it.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Post Reply