SAB closes moments after starting

[nodave]

SHORT VERSION - I messed something up, now SAB closes almost right after I start it. What can I check to find the problem?

Hello, I was running SAB version 4.0.3 without any problems. I use windows 11 pro. I then installed the latest version - 4.1.0 and it was working.
I was tweaking my home network and moved this computer with SAB to a VLAN. I'm novice with networking and needless to say messed something up.
I have since placed this computer back on the regular lan. Now when I open SAB I can see the icon in the system tray and I can click it but no matter what I do it closes and does nothing. I have checked to make sure there is just one instance of SAB running. I have also tried opening localhost:8080 in the web browser, and I edited the ini file to change the port to 8089 and that didn't work either. I uninstalled the latest SAB version and re-installed version 4.0.3 to see if that would fix it, but I'm still having problems.

In searching for an answer I came across someone with the same problem and they were advised to use CMD to open the sab-console and past what it reported. So, if this information means anything to anyone, here it is.

The forum does not allow new users to post links, so I am unable to paste here the log. I tried to edit the 127 0 0 1 so that it didn't show as a link, but I dont know what Im doing and it still wont allow me to paste.

[sander]

Yes: open a CMD box, go to Program FIles ... SABnzbd, and the start/type sabnzbd-console.exe

Post the full output to pastebin.com, and post the URL here like pastebin . com / asjdlfkjlakjsdf

[nodave]

Thank you for your response. I went and did a fresh windows install, Win 11 pro, and a fresh install of sabnzbd. It worked fine initially, but now the problem has started again. Here is the sabnzbd-console for the fresh install.

pastebin . com / 65gx27gu

Quick question, I have a synology ds920+ Would installing this in a docker on it be more stable, or am I just not doing something right?

[sander]

OK: https://pastebin.com/65gx27gu

portend.Timeout: Port 8089 not bound on 127.0.0.1.

SABnzbd cannot "bind" (connect) to port 8089 on your computer. This is probably caused by a firewall or virusscanner on your Windows PC. So disable your firewall and/or virusscanner and try again.

BTW: port 8089 is non-standard; standard is 8080. So if you a fresh install of Windows (right?), this is strange.

Code: Select all

2023-10-01 21:21:48,465::INFO::[SABnzbd:1430] Starting web-interface on 127.0.0.1:8089
2023-10-01 21:21:48,465::INFO::[_cplogging:213] [01/Oct/2023:21:21:48] ENGINE Bus STARTING
2023-10-01 21:21:53,624::INFO::[notifier:123] Sending notification: Error - [01/Oct/2023:21:21:53] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x0000024611F0C950>>
Traceback (most recent call last):
  File "cherrypy\process\wspbus.py", line 230, in publish
  File "cherrypy\_cpserver.py", line 180, in start
  File "cherrypy\process\servers.py", line 184, in start
  File "cherrypy\process\servers.py", line 260, in wait
  File "portend.py", line 159, in occupied
portend.Timeout: Port 8089 not bound on 127.0.0.1.
 (type=error, job_cat=None)
2023-10-01 21:21:53,623::ERROR::[_cplogging:213] [01/Oct/2023:21:21:53] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x0000024611F0C950>>
Traceback (most recent call last):
  File "cherrypy\process\wspbus.py", line 230, in publish
  File "cherrypy\_cpserver.py", line 180, in start
  File "cherrypy\process\servers.py", line 184, in start
  File "cherrypy\process\servers.py", line 260, in wait
  File "portend.py", line 159, in occupied
portend.Timeout: Port 8089 not bound on 127.0.0.1.
 
2023-10-01 21:21:53,625::ERROR::[_cplogging:213] [01/Oct/2023:21:21:53] ENGINE Shutting down due to error in start listener:
Traceback (most recent call last):
  File "cherrypy\process\wspbus.py", line 268, in start
  File "cherrypy\process\wspbus.py", line 248, in publish
cherrypy.process.wspbus.ChannelFailures: Timeout('Port 8089 not bound on 127.0.0.1.')

[sander]

Quick question, I have a synology ds920+ Would installing this in a docker on it be more stable, or am I just not doing something right?

SABnzbd on Windows is very stable. But your firewall/virusscanner is forbidding it to work.
SABnzbd straight on Synology is very nice too. And no firewall/virusscanner disturbing stuff
However, SABnzbd in Docker on Synology brings its own problems, because of docker isolation.
You can always try.

[nodave]

Thank you sander, I appreciate the help and insight. I think I will stick with windows.

I will try out changing ports and maybe seeing if I can enable the port in my firewall.


edit - I changed sab to the host computers static IP and now it works. thank you again.