Sab exe not working but Console is!?

[stuza]

Hi All,

weird one where Sab has suddenly decided after years that it will not start properly from shortcut or double clicking the .exe directly, but works perfectly OK when opening the Sab console.

The arrow appears in the system tray as yellow, turns green then shuts down a second or 2 later.

I've uninstalled, deleted all directories that remained, downloaded a new copy then reinstalled and copied back the config including my change of port to 8087.

On Windows 11 Pro. Sab wrench tests https://prnt.sc/OaGjlGoARf4e


As I said, it's still perfectly usable, I just have to launch the Console instead and have the command box constantly updating with text.


Thanks for any help/clues!

The error is as follows:

2023-07-01 12:00:01,932::INFO::[SABnzbd:475] 7za binary... found (C:\Program Files\SABnzbd\win\7zip\7za.exe)
2023-07-01 12:00:01,932::INFO::[SABnzbd:1439] Starting web-interface on 127.0.0.1:8087
2023-07-01 12:00:01,933::INFO::[_cplogging:213] [01/Jul/2023:12:00:01] ENGINE Bus STARTING
2023-07-01 12:00:07,127::INFO::[notifier:123] Sending notification: Error - [01/Jul/2023:12:00:07] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x00000262180824D0>>
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 8087 not bound on 127.0.0.1.
(type=error, job_cat=None)
2023-07-01 12:00:07,127::ERROR::[_cplogging:213] [01/Jul/2023:12:00:07] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x00000262180824D0>>
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 8087 not bound on 127.0.0.1.

2023-07-01 12:00:07,127::ERROR::[_cplogging:213] [01/Jul/2023:12:00:07] 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 8087 not bound on 127.0.0.1.')

2023-07-01 12:00:07,127::INFO::[_cplogging:213] [01/Jul/2023:12:00:07] ENGINE Bus STOPPING
2023-07-01 12:00:07,128::INFO::[_cplogging:213] [01/Jul/2023:12:00:07] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('192.168.50.77', 8087)) already shut down
2023-07-01 12:00:07,128::INFO::[_cplogging:213] [01/Jul/2023:12:00:07] ENGINE Bus STOPPED
2023-07-01 12:00:07,128::INFO::[_cplogging:213] [01/Jul/2023:12:00:07] ENGINE Bus EXITING
2023-07-01 12:00:07,128::INFO::[_cplogging:213] [01/Jul/2023:12:00:07] ENGINE Bus EXITED

[sander]

On Windows, so my first suspect would be firewall and virusscanner not allowing to bind to a port.

[stuza]

But it's working fine if I just launch with the console. Would fw not block both?

[sander]

Who knows? Heuristic analysis by your virusscannner or firewall?

So: try?

[stuza]

Seems OK to me, all 7 entries have access.

https://prnt.sc/A_4DtEqiOAPG

[sander]

Seems OK to me, all 7 entries have access.

You can verify that statement / hypothesis by temporarily disabling your firewall and virusscanner

[stuza]

Seems OK to me, all 7 entries have access.

You can verify that statement / hypothesis by temporarily disabling your firewall and virusscanner

Verified!

AV and Defender both off and same result.