Sab fails to initialize - IOError
Posted: June 10th, 2016, 11:21 pm
Hi,
Sab has been running great until tonight. The engine keeps shutting down:
2016-06-10 23:32:20,102::INFO::[_cplogging:216] [10/Jun/2016:23:32:20] ENGINE Started monitor thread '_TimeoutMonitor'.
2016-06-10 23:33:10,316::ERROR::[_cplogging:216] [10/Jun/2016:23:33:10] ENGINE Error in 'start' listener <bound method ServerAdapter.start of <cherrypy.process.servers.ServerAdapter object at 0x0304D4D0>>
Traceback (most recent call last):
File "cherrypy\process\wspbus.pyo", line 205, in publish
File "cherrypy\process\servers.pyo", line 177, in start
File "cherrypy\process\servers.pyo", line 233, in wait
File "cherrypy\process\servers.pyo", line 459, in wait_for_occupied_port
IOError: Port 8080 not bound on '127.0.0.1'
From another post with the same problem suggested to try starting it with the SABnzbd-console.exe. It worked as it should, so I tried changing the port number and then starting it the normal way a couple of times but it still comes back with the IOError. Any suggestions on ow to fix this?
Sab has been running great until tonight. The engine keeps shutting down:
2016-06-10 23:32:20,102::INFO::[_cplogging:216] [10/Jun/2016:23:32:20] ENGINE Started monitor thread '_TimeoutMonitor'.
2016-06-10 23:33:10,316::ERROR::[_cplogging:216] [10/Jun/2016:23:33:10] ENGINE Error in 'start' listener <bound method ServerAdapter.start of <cherrypy.process.servers.ServerAdapter object at 0x0304D4D0>>
Traceback (most recent call last):
File "cherrypy\process\wspbus.pyo", line 205, in publish
File "cherrypy\process\servers.pyo", line 177, in start
File "cherrypy\process\servers.pyo", line 233, in wait
File "cherrypy\process\servers.pyo", line 459, in wait_for_occupied_port
IOError: Port 8080 not bound on '127.0.0.1'
From another post with the same problem suggested to try starting it with the SABnzbd-console.exe. It worked as it should, so I tried changing the port number and then starting it the normal way a couple of times but it still comes back with the IOError. Any suggestions on ow to fix this?