SABnzbd Forums

My sab crashes whenever I have a large queue, typically 50+. I've checked the log files and can't see anything, just start up info when I restart it.

2014-07-28 14:12:35,385::INFO::[_cplogging:55] [28/Jul/2014:14:12:35] ENGINE Bus STARTING
2014-07-28 14:12:35,394::INFO::[_cplogging:55] [28/Jul/2014:14:12:35] ENGINE Started monitor thread '_TimeoutMonitor'.
2014-07-28 14:12:35,598::INFO::[_cplogging:55] [28/Jul/2014:14:12:35] ENGINE Serving on ::1:8080
2014-07-28 14:12:35,803::INFO::[_cplogging:55] [28/Jul/2014:14:12:35] ENGINE Serving on 0.0.0.0:8080
2014-07-28 14:12:35,805::INFO::[_cplogging:55] [28/Jul/2014:14:12:35] ENGINE Bus STARTED

crashed sometime between this and restarting

2014-07-28 15:04:25,858::INFO::[_cplogging:55] [28/Jul/2014:15:04:25] ENGINE Bus STARTING
2014-07-28 15:04:25,865::INFO::[_cplogging:55] [28/Jul/2014:15:04:25] ENGINE Started monitor thread '_TimeoutMonitor'.
2014-07-28 15:04:26,167::INFO::[_cplogging:55] [28/Jul/2014:15:04:26] ENGINE Serving on ::1:8080
2014-07-28 15:04:26,371::INFO::[_cplogging:55] [28/Jul/2014:15:04:26] ENGINE Serving on 0.0.0.0:8080
2014-07-28 15:04:26,371::INFO::[_cplogging:55] [28/Jul/2014:15:04:26] ENGINE Bus STARTED

any thoughts, or is there any more details I can get to help you?

Thanks

How do you SAB crashed?

it just stops, ie not running at all and is not in task manager, no errors or warnings

TheThingIs wrote:it just stops, ie not running at all and is not in task manager, no errors or warnings

So ... you're on Windows?

If so, stop SABnzbd, open a CMD box, find and run sabnzbd-console.exe. When it crashes, post the CMD-output here in this forum.

ok done that so will wait for it to crash again. In the meantime, I found the .exe log if this helps any...

Exception in thread Thread-3:
Traceback (most recent call last):
File "threading.pyo", line 488, in __bootstrap_inner
File "sabnzbd\downloader.pyo", line 417, in run
error: (10038, 'An operation was attempted on something that is not a socket')

Python WNDPROC handler failed
Traceback (most recent call last):
File "sabnzbd\utils\systrayiconthread.pyo", line 166, in notify
File "sabnzbd\utils\systrayiconthread.pyo", line 178, in show_menu
pywintypes.error: (0, 'SetForegroundWindow', 'No error message is available')
Python WNDPROC handler failed
TypeError: restart() takes exactly 2 arguments (5 given)
Python WNDPROC handler failed
Traceback (most recent call last):
File "sabnzbd\utils\systrayiconthread.pyo", line 166, in notify
File "sabnzbd\utils\systrayiconthread.pyo", line 178, in show_menu
pywintypes.error: (0, 'SetForegroundWindow', 'No error message is available')
Python WNDPROC handler failed
Traceback (most recent call last):
File "sabnzbd\utils\systrayiconthread.pyo", line 166, in notify
File "sabnzbd\utils\systrayiconthread.pyo", line 176, in show_menu
pywintypes.error: (5, 'GetCursorPos', 'Access is denied.')
Python WNDPROC handler failed
Traceback (most recent call last):
File "sabnzbd\utils\systrayiconthread.pyo", line 166, in notify
File "sabnzbd\utils\systrayiconthread.pyo", line 176, in show_menu
pywintypes.error: (5, 'GetCursorPos', 'Access is denied.')

This is too much Windows-only (systray) for me to understand.

I don't have a clue.
Just threw a hundred NZB in the queue: no problem.
Does the problem go away when you restart SABnzbd?
Which Windows version do you use?

Some googling tells me that it's an obscure and likely unsolved bug in a software library that we use.
I cannot fix the problem, but I can prevent the crash in the next release.
In the mean time you can choose to disable the SysTray icon instead.
Set Config->Special->win_menu to 0

will do. It crashed again but nothing in the cmd window, although I did get a window pop up simply saying that sab had crashed, no other info tho.

I am getting this also after updating to the lastest release on windows.

Eventlog says this:
Faulting application name: SABnzbd-service.exe, version: 0.7.18.0, time stamp: 0x4917df95
Faulting module name: _yenc.pyd, version: 0.0.0.0, time stamp: 0x44ddea19
Exception code: 0xc0000005
Fault offset: 0x000019e7
Faulting process id: 0x11f8
Faulting application start time: 0x01cfadb00e7006c4
Faulting application path: C:\Winprg\SABnzbd\SABnzbd-service.exe
Faulting module path: C:\Winprg\SABnzbd\lib\_yenc.pyd
Report Id: e7b55051-19a3-11e4-bd9e-00155d00aa38

Logs says this:

2014-08-01 19:58:23,292::ERROR::[_cplogging:55] [01/Aug/2014:19:58:23] Traceback (most recent call last):
File "cherrypy\_cprequest.pyo", line 98, in run
File "cherrypy\_cprequest.pyo", line 58, in __call__
File "cherrypy\lib\encoding.pyo", line 64, in encode
File "cherrypy\lib\encoding.pyo", line 132, in find_acceptable_charset
File "cherrypy\lib\encoding.pyo", line 88, in encode_string
MemoryError


MemoryError...
Watching in task manager I see the SABnzbd-service.exe junk memory until it stops. Happens over and over.

Combination of a large queue and bad memory handling maybe?

Now if only there was a 64 bit version of this, it might never crash like this and use the available memory instead. I think it crashes right around 1.7Gb RAM.

Emptying the queue seemed to solve it. Was a weird error where the queue just grew and grew re-adding RSS items, the same ones over and over.

Maybe https://forums.sabnzbd.org/viewtopic.ph ... t=0#p10167 is worth a read & try?

I was getting the exact same problems until recently. Many of the same log errors.

The issue was that I was using a flash drive as my download drive, and then moving to a hard drive. The flash drive (or the USB port) apparently could not handle all the read/write requests. Also, my completed and incomplete folders were on the same flash drive, and then couch potato would process files as SAB was downloading.

Upon switching to a regular e-sata hard drive, all issues disappeared. I tested it by creating a 300 item queue, and no problems.

So.. I would suggest checking your disk health, or if you are also using flash memory, get rid of it and use a regular hard drive.