Page 1 of 1

SABnzdb+ worked perfect, then stopped working with error to check logfile

Posted: April 21st, 2011, 7:39 pm
by NadsRSnug
I am hoping someone can point me in the right direction.  I had my SABnzdb+ server working perfect, schedules and everything, just peachy.  All of a sudden my Windows7 x64 system got the notorious blue screen (for what reason I do not know) and now I get an error message to check the sabnzbd.exe.log file. I look at it and do not understand anything other than I know the .py files are some kind of programming language.

I did make changes the the sabnzbd.ini file way back when when I inititially installed everything, but haven't touched it since.  The reason I say this is because I looked through the forum and found something relating to just removing it if you didn't make any changes to it, but I did (like the port number, directories, etc.) 

The log file is below.  Please someone help.  I am not very good at this stuff, and just setting this server up really was a learning experience.  I just see a lot of "scheduler errors".  I sure hope to God I don't have to start from scratch.

ERROR DURING SCHEDULER EXECUTION list index out of range
Traceback (most recent call last):
  File "sabnzbd\utils\kronos.pyo", line 277, in _run
  File "sched.pyo", line 108, in run
  File "sabnzbd\utils\kronos.pyo", line 104, in __delayfunc
  File "sabnzbd\utils\kronos.pyo", line 269, in _getqueuetoptime
IndexError: list index out of range

--------------------
ERROR DURING SCHEDULER EXECUTION list index out of range
Traceback (most recent call last):
  File "sabnzbd\utils\kronos.pyo", line 277, in _run
  File "sched.pyo", line 108, in run
  File "sabnzbd\utils\kronos.pyo", line 104, in __delayfunc
  File "sabnzbd\utils\kronos.pyo", line 269, in _getqueuetoptime
IndexError: list index out of range

--------------------
ERROR DURING SCHEDULER EXECUTION list index out of range
Traceback (most recent call last):
  File "sabnzbd\utils\kronos.pyo", line 277, in _run
  File "sched.pyo", line 108, in run
  File "sabnzbd\utils\kronos.pyo", line 104, in __delayfunc
  File "sabnzbd\utils\kronos.pyo", line 269, in _getqueuetoptime
IndexError: list index out of range

--------------------
Exception in thread CP WSGIServer Thread-24:
Traceback (most recent call last):
  File "threading.pyo", line 488, in __bootstrap_inner
  File "cherrypy\wsgiserver\__init__.pyo", line 1280, in run
  File "cherrypy\wsgiserver\__init__.pyo", line 1200, in communicate
  File "cherrypy\wsgiserver\__init__.pyo", line 601, in simple_response
  File "cherrypy\wsgiserver\__init__.pyo", line 1114, in sendall
  File "cherrypy\wsgiserver\__init__.pyo", line 1066, in _safe_call
  File "cherrypy\wsgiserver\__init__.pyo", line 736, in sendall
  File "cherrypy\wsgiserver\__init__.pyo", line 1117, in send
  File "cherrypy\wsgiserver\__init__.pyo", line 1096, in _safe_call
FatalSSLAlert: [('SSL routines', 'SSL3_WRITE_BYTES', 'ssl handshake failure')]

Exception in thread CP WSGIServer Thread-25:
Traceback (most recent call last):
  File "threading.pyo", line 488, in __bootstrap_inner
  File "cherrypy\wsgiserver\__init__.pyo", line 1280, in run
  File "cherrypy\wsgiserver\__init__.pyo", line 1200, in communicate
  File "cherrypy\wsgiserver\__init__.pyo", line 601, in simple_response
  File "cherrypy\wsgiserver\__init__.pyo", line 1114, in sendall
  File "cherrypy\wsgiserver\__init__.pyo", line 1066, in _safe_call
  File "cherrypy\wsgiserver\__init__.pyo", line 736, in sendall
  File "cherrypy\wsgiserver\__init__.pyo", line 1117, in send
  File "cherrypy\wsgiserver\__init__.pyo", line 1096, in _safe_call
FatalSSLAlert: [('SSL routines', 'SSL23_WRITE', 'ssl handshake failure')]

Exception in thread CP WSGIServer Thread-29:
Traceback (most recent call last):
  File "threading.pyo", line 488, in __bootstrap_inner
  File "cherrypy\wsgiserver\__init__.pyo", line 1280, in run
  File "cherrypy\wsgiserver\__init__.pyo", line 1200, in communicate
  File "cherrypy\wsgiserver\__init__.pyo", line 601, in simple_response
  File "cherrypy\wsgiserver\__init__.pyo", line 1114, in sendall
  File "cherrypy\wsgiserver\__init__.pyo", line 1066, in _safe_call
  File "cherrypy\wsgiserver\__init__.pyo", line 736, in sendall
  File "cherrypy\wsgiserver\__init__.pyo", line 1117, in send
  File "cherrypy\wsgiserver\__init__.pyo", line 1096, in _safe_call
FatalSSLAlert: [('SSL routines', 'SSL3_WRITE_BYTES', 'ssl handshake failure')]

Traceback (most recent call last):
  File "SABnzbd.py", line 1257, in
  File "SABnzbd.py", line 869, in main
  File "cherrypy\process\servers.pyo", line 228, in check_port
socket.gaierror: (11004, 'getaddrinfo failed')
Traceback (most recent call last):
  File "SABnzbd.py", line 1257, in
  File "SABnzbd.py", line 869, in main
  File "cherrypy\process\servers.pyo", line 228, in check_port
socket.gaierror: (11004, 'getaddrinfo failed')
Traceback (most recent call last):
  File "SABnzbd.py", line 1257, in
  File "SABnzbd.py", line 869, in main
  File "cherrypy\process\servers.pyo", line 228, in check_port
socket.gaierror: (11004, 'getaddrinfo failed')
Traceback (most recent call last):
  File "SABnzbd.py", line 1257, in
  File "SABnzbd.py", line 869, in main
  File "cherrypy\process\servers.pyo", line 228, in check_port
socket.gaierror: (11004, 'getaddrinfo failed')
Traceback (most recent call last):
  File "SABnzbd.py", line 1257, in
  File "SABnzbd.py", line 869, in main
  File "cherrypy\process\servers.pyo", line 228, in check_port
socket.gaierror: (11004, 'getaddrinfo failed')

Re: SABnzdb+ worked perfect, then stopped working with error to check logfile

Posted: April 22nd, 2011, 1:56 pm
by shypike
Stop SABnzbd and check your sabnzbd.ini file for irregularities.
Especially the line starting with
schedlines =
Remove it and set schedules again.

The error socket.gaierror: (11004, 'getaddrinfo failed') indicates that
DNS might be of its rocker.
Which host address do you use for SABnzbd?

Re: SABnzdb+ worked perfect, then stopped working with error to check logfile

Posted: April 23rd, 2011, 1:00 am
by NadsRSnug
I did reboot and tried as best I could to test DNS, and everything I tried to ping I could.  I just tried renaming the sabnzbd.ini file to sabnzbd.old and tried to start sabnzdb.exe and it did seem to do better by going to a setup web page on port 8085.  I am going to try and look to see if I can find anything.  I do know I enabled both http on port 8085 and https on port 9090 and only enabled https, and maybe by enabling both of them caused this problem. 

currently, my schedlines look like this:schedlines = ,

By removing that line completely, I still get the error to look at the sabnzbd.exe.log file.

I DON'T

Re: SABnzdb+ worked perfect, then stopped working with error to check logfile

Posted: April 23rd, 2011, 1:05 am
by NadsRSnug
I did reboot and tried as best I could to test DNS, and everything I tried to ping I could.  I just tried renaming the sabnzbd.ini file to sabnzbd.old and tried to start sabnzdb.exe and it did seem to do better by going to a setup web page on port 8085.  I am going to try and look to see if I can find anything.  I do know I enabled both http on port 8085 and https on port 9090 and only enabled https, and maybe by enabling both of them caused this problem. 

currently, my schedlines look like this:schedlines = ,

By removing that line completely, I still get the error to look at the sabnzbd.exe.log file.

I DON'T want to sound completely stupid, but I am not sure what you mean by "Which host address so you use for Sabnzbd?"  I  think you are asking, the entry in the sabnzdb.ini with host = is :host = http://172.19.1.3

I will simply save my current .ini file to a backup and see if I can't start chaning some entires like changing the host = 0.0.0.0 or blank.

Thank you very much for responding.

Re: SABnzdb+ worked perfect, then stopped working with error to check logfile

Posted: April 23rd, 2011, 1:21 am
by NadsRSnug
GREAT NEWS!!!!  I changed my host =172.10.1.3 to host ="" and it worked ... everything is working including SADCommand on the iPad. 

You let me in the right direction by referencing the host.


Thank you thank you thank you.

Re: SABnzdb+ worked perfect, then stopped working with error to check logfile

Posted: April 23rd, 2011, 4:01 am
by shypike
The error message will be improved in the next release.
But we're also a limited to the amount of info the OS actually gives us.