Page 1 of 1

Sab fails to initialize - IOError

Posted: June 10th, 2016, 11:21 pm
by silverstone
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?

Re: Sab fails to initialize - IOError

Posted: June 11th, 2016, 10:38 am
by shypike
Did you reboot your system yet?
Some process is using the same port as SABnzbd wants to use.

Re: Sab fails to initialize - IOError

Posted: June 11th, 2016, 4:10 pm
by silverstone
Reboot didn't help. It really doesn't make since why the SABnzbd-console.exe will work but not SABnzbd.exe. What's the difference?
Come to think of it, I just upgraded. I'm going to rollback to an older version and see if that fixes it.
In the meantime, do you know of something else I could try?

Re: Sab fails to initialize - IOError

Posted: June 11th, 2016, 4:38 pm
by shypike
There's no difference in behaviour between SABnzbd.exe and SABnzbd-console.exe
except that the latter produces visible log output.

Re: Sab fails to initialize - IOError

Posted: June 11th, 2016, 7:18 pm
by silverstone
I tried rolling back to v1.0 but the same error is coming up. This is totally baffling.
I guess the only solution at this point is to reimage the drive and setup Sab from scratch.
It's going to be a long night.

UPDATE: Just finished reimaging the drive and setting up Sab.
Everything is working as it should and hopefully that issue was just a fluke.