4.1.0 crashing on macOS Sonoma

[taylorjamesbarr]

I recently updated my M1 Mac Mini that hosts SABnzbd and Plex along with Sonarr and Radarr. These applications are all installed in macOS itself, and there is no Docker or VM involved.

The Mac is now running macOS Sonoma 14.0, and I noticed it had an update for SABnzbd 4.1.0 as well. I updated both, but I have been noticing issues accessing the web GUI either on the local machine, or via the local network.

I'll get the standard Lost connection to SABnzbd.. In case of SABnzbd restart this screen will disappear automatically error message, but whereas I used to see this before, it does not appear to restart. The logs are very confusing for me (just a bit of a nerd who likes playing around, but no experience with logs or coding).

I tried rolling back to the previous stable release of SABnzbd, but that made no change. Can anyone help figure out what is causing the web GUI to crash? Or is it the entire application crashing as well? I've tried doing an uninstall and reinstall (and then I did restore from backup), but that did not help. Could a true clean install without restoring from backup help?

Based on other posts on the forum, it looks like the web server is crashing, but I have no idea why.

Logs here: pastebin . com / f6FV9zDx

[sander]

So https://pastebin.com/f6FV9zDx

Strange stuff going on.

Code: Select all

2023-10-07 19:47:24,893::INFO::[notifier:123] Sending notification: Warning - Could not restore backup (type=warning, job_cat=None)
2023-10-07 19:47:24,893::WARNING::[config:1101] Could not restore backup
2023-10-07 19:47:24,893::INFO::[config:1102] Traceback: 
Traceback (most recent call last):
  File "sabnzbd/config.py", line 1080, in restore_config_backup
  File "sabnzbd/decorators.py", line 39, in call_func
  File "sabnzbd/config.py", line 870, in read_config
  File "sabnzbd/config.py", line 928, in _read_config
  File "sabnzbd/config.py", line 186, in set
  File "sabnzbd/config.py", line 128, in set
  File "sabnzbd/dirscanner.py", line 98, in newspeed
  File "sabnzbd/dirscanner.py", line 128, in start_scanner
  File "asyncio/tasks.py", line 926, in run_coroutine_threadsafe
  File "asyncio/base_events.py", line 806, in call_soon_threadsafe
  File "asyncio/base_events.py", line 519, in _check_closed
RuntimeError: Event loop is closed

and a lot:

Code: Select all

OSError: [Errno 57] Socket is not connected

The Mac is now running macOS Sonoma 14.0, and I noticed it had an update for SABnzbd 4.1.0 as well. I updated both,

So ... caused by macOS Sonoma 14.0 (preventing some things ... killing SAB's port binding after some time?) or SABnzbd 4.1.0 (which would be weird, because no changes to network), or combination?

Can you back to an earlier version of SABnzbd? I don't think it will help, but just to rule that out?

Have you got a Mac with an earlier MacOS?

[sander]

Also:

While SAB is running, and accessible, do this:

To use netstat, open the Terminal application and type “netstat -an | grep LISTEN.” This will show you a list of all the open ports on your Mac, along with the process ID verification service (PID) and name of the application that's using each port.

As soons as SAB is not accissble anymore, do the same

Report results here.

[taylorjamesbarr]

Can you back to an earlier version of SABnzbd? I don't think it will help, but just to rule that out?

I rolled back to 4.0.3 but that doesn't resolve any of the issues. Same things occur from what I can see.

Have you got a Mac with an earlier MacOS?

Regrettably I updated my other Mac as well to Sonoma, so I don't have anything running Ventura to test anymore.

If it's worth anything, the socket errors would frequently occur prior to Sonoma, but SABnzbd would recover and self-restart. It appears that doesn't happen anymore and I have to force restart it.

While SAB is running, and accessible, do this:

To use netstat, open the Terminal application and type “netstat -an | grep LISTEN.” This will show you a list of all the open ports on your Mac, along with the process ID verification service (PID) and name of the application that's using each port.

As soons as SAB is not accissble anymore, do the same

Will do! Just need to wait for it to crash next. It was stable for a few hours last night and then overnight it presented those errors and wasn't accessible.

[taylorjamesbarr]

Rather annoyingly, it hasn't happened since I posted about it in this thread, despite it being constant beforehand. I'll continue to monitor this, but I should be happy that it has stopped happening for now.

I'll post the results should it occur again.

[taylorjamesbarr]

Just crashed now. Here are the results while it was running and accessible:

Code: Select all

taylor@Taylors-Mac-mini-2 ~ % netstat -an | grep LISTEN
tcp46      0      0  *.7878                 *.*                    LISTEN     
tcp4       0      0  *.8080                 *.*                    LISTEN     
tcp4       0      0  *.6789                 *.*                    LISTEN     
tcp4       0      0  *.8989                 *.*                    LISTEN     
tcp4       0      0  *.32469                *.*                    LISTEN     
tcp4       0      0  *.1432                 *.*                    LISTEN     
tcp4       0      0  127.0.0.1.32600        *.*                    LISTEN     
tcp4       0      0  127.0.0.1.49166        *.*                    LISTEN     
tcp4       0      0  *.8181                 *.*                    LISTEN     
tcp4       0      0  127.0.0.1.32401        *.*                    LISTEN     
tcp46      0      0  *.32400                *.*                    LISTEN     
tcp4       0      0  *.88                   *.*                    LISTEN     
tcp6       0      0  *.88                   *.*                    LISTEN     
tcp4       0      0  *.445                  *.*                    LISTEN     
tcp6       0      0  *.445                  *.*                    LISTEN     
tcp4       0      0  *.5900                 *.*                    LISTEN     
tcp6       0      0  *.5900                 *.*                    LISTEN 

And the results after it stopped working;

Code: Select all

taylor@Taylors-Mac-mini-2 ~ % netstat -an | grep LISTEN
tcp46      0      0  *.7878                 *.*                    LISTEN     
tcp4       0      0  *.8989                 *.*                    LISTEN     
tcp4       0      0  *.8181                 *.*                    LISTEN     
tcp4       0      0  *.6789                 *.*                    LISTEN     
tcp4       0      0  *.88                   *.*                    LISTEN     
tcp6       0      0  *.88                   *.*                    LISTEN     
tcp4       0      0  *.445                  *.*                    LISTEN     
tcp6       0      0  *.445                  *.*                    LISTEN     
tcp4       0      0  *.5900                 *.*                    LISTEN     
tcp6       0      0  *.5900                 *.*                    LISTEN

The Terminal output doesn't appear to return the name of the process, but I hope that was helpful.

[taylorjamesbarr]

Here are the logs for the time it crashed:

Code: Select all

2023-10-13 22:18:49,746::WARNING::[_cplogging:213] [13/Oct/2023:22:18:49] ENGINE socket.error 57
Traceback (most recent call last):
  File "cheroot/server.py", line 1277, in communicate
  File "cheroot/server.py", line 710, in parse_request
  File "cheroot/server.py", line 751, in read_request_line
  File "cheroot/server.py", line 301, in readline
  File "_pyio.py", line 574, in readline
  File "_pyio.py", line 553, in nreadahead
  File "_pyio.py", line 1149, in peek
  File "_pyio.py", line 1156, in _peek_unlocked
  File "socket.py", line 706, in readinto
OSError: [Errno 57] Socket is not connected

2023-10-13 22:18:49,746::WARNING::[_cplogging:213] [13/Oct/2023:22:18:49] ENGINE socket.error 57
Traceback (most recent call last):
  File "cheroot/server.py", line 1277, in communicate
  File "cheroot/server.py", line 710, in parse_request
  File "cheroot/server.py", line 751, in read_request_line
  File "cheroot/server.py", line 301, in readline
  File "_pyio.py", line 574, in readline
  File "_pyio.py", line 553, in nreadahead
  File "_pyio.py", line 1149, in peek
  File "_pyio.py", line 1156, in _peek_unlocked
  File "socket.py", line 706, in readinto
OSError: [Errno 57] Socket is not connected

To confirm there have been no network or environmental changes that align with the issue starting. It's very odd as it has been running fine for 3 days since my original post and just occurred again now.

[safihre]

In your log I see both 0.0.0.0 and 127.0.0.1 (localhost), did you try both and did it crash with both settings?

[taylorjamesbarr]

Yeah I basically saw the crash and then clicked on the SABnzbd menu icon and tried the various restart options to see if they would help fix the issue. I then saw somewhere on another post that the host should be 0.0.0.0 in most situations. Both resulted in the same thing for me - at least what I observed. It's on 0.0.0.0 at the moment.

[safihre]

Maybe you can try a different port, and if you don't need SABnzbd to be available from your network, I would suggest to set the host to 'localhost'.

[taylorjamesbarr]

Happy to switch to another port and give that a go. Because it runs on a headless Mac Mini, I do like it to be accessible via the network so I can easily jump on and check from another machine. Any port recommendation or legit just anything?

[safihre]

It can be anything.
Easy to rember ones can be 5555, 6060 or 8888, etc

[taylorjamesbarr]

Have just changed it to 5555 and will monitor and report back. Physically moving the entire machine from New Zealand to Australia with myself in about 18 hours time - so we'll see if the move impacts anything negatively - hoping not.

[taylorjamesbarr]

Still experiencing crashes on this now - looking more frequent as well. It has started doing it every few minutes in the last hour.

Code: Select all

2023-10-14 23:50:39,516::INFO::[_cplogging:213] [14/Oct/2023:23:50:39] ENGINE Bus STOPPING
2023-10-14 23:50:39,951::INFO::[_cplogging:213] [14/Oct/2023:23:50:39] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 5555)) shut down
2023-10-14 23:50:39,951::INFO::[_cplogging:213] [14/Oct/2023:23:50:39] ENGINE Bus STOPPED
2023-10-14 23:50:39,951::INFO::[_cplogging:213] [14/Oct/2023:23:50:39] ENGINE Bus EXITING
2023-10-14 23:50:39,952::INFO::[_cplogging:213] [14/Oct/2023:23:50:39] ENGINE Bus EXITED
2023-10-14 23:50:40,640::INFO::[_cplogging:213] [14/Oct/2023:23:50:40] ENGINE Bus STARTING
2023-10-14 23:50:40,747::INFO::[_cplogging:213] [14/Oct/2023:23:50:40] ENGINE Serving on http://0.0.0.0:5555
2023-10-14 23:50:40,747::INFO::[_cplogging:213] [14/Oct/2023:23:50:40] ENGINE Bus STARTED
2023-10-14 23:53:03,408::WARNING::[_cplogging:213] [14/Oct/2023:23:53:03] ENGINE socket.error 57
Traceback (most recent call last):
  File "cheroot/server.py", line 1277, in communicate
  File "cheroot/server.py", line 710, in parse_request
  File "cheroot/server.py", line 751, in read_request_line
  File "cheroot/server.py", line 301, in readline
  File "_pyio.py", line 574, in readline
  File "_pyio.py", line 553, in nreadahead
  File "_pyio.py", line 1149, in peek
  File "_pyio.py", line 1156, in _peek_unlocked
  File "socket.py", line 706, in readinto
OSError: [Errno 57] Socket is not connected

2023-10-14 23:53:03,408::WARNING::[_cplogging:213] [14/Oct/2023:23:53:03] ENGINE socket.error 57
Traceback (most recent call last):
  File "cheroot/server.py", line 1277, in communicate
  File "cheroot/server.py", line 710, in parse_request
  File "cheroot/server.py", line 751, in read_request_line
  File "cheroot/server.py", line 301, in readline
  File "_pyio.py", line 574, in readline
  File "_pyio.py", line 553, in nreadahead
  File "_pyio.py", line 1149, in peek
  File "_pyio.py", line 1156, in _peek_unlocked
  File "socket.py", line 706, in readinto
OSError: [Errno 57] Socket is not connected

2023-10-14 23:53:44,178::INFO::[_cplogging:213] [14/Oct/2023:23:53:44] ENGINE Bus STOPPING
2023-10-14 23:53:44,574::INFO::[_cplogging:213] [14/Oct/2023:23:53:44] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 5555)) shut down
2023-10-14 23:53:44,575::INFO::[_cplogging:213] [14/Oct/2023:23:53:44] ENGINE Bus STOPPED
2023-10-14 23:53:44,575::INFO::[_cplogging:213] [14/Oct/2023:23:53:44] ENGINE Bus EXITING
2023-10-14 23:53:44,575::INFO::[_cplogging:213] [14/Oct/2023:23:53:44] ENGINE Bus EXITED
2023-10-14 23:53:45,316::INFO::[_cplogging:213] [14/Oct/2023:23:53:45] ENGINE Bus STARTING
2023-10-14 23:53:45,423::INFO::[_cplogging:213] [14/Oct/2023:23:53:45] ENGINE Serving on http://0.0.0.0:5555
2023-10-14 23:53:45,423::INFO::[_cplogging:213] [14/Oct/2023:23:53:45] ENGINE Bus STARTED
2023-10-14 23:55:15,806::WARNING::[_cplogging:213] [14/Oct/2023:23:55:15] ENGINE socket.error 57
Traceback (most recent call last):
  File "cheroot/server.py", line 1277, in communicate
  File "cheroot/server.py", line 710, in parse_request
  File "cheroot/server.py", line 751, in read_request_line
  File "cheroot/server.py", line 301, in readline
  File "_pyio.py", line 574, in readline
  File "_pyio.py", line 553, in nreadahead
  File "_pyio.py", line 1149, in peek
  File "_pyio.py", line 1156, in _peek_unlocked
  File "socket.py", line 706, in readinto
OSError: [Errno 57] Socket is not connected

2023-10-14 23:55:15,807::WARNING::[_cplogging:213] [14/Oct/2023:23:55:15] ENGINE socket.error 57
Traceback (most recent call last):
  File "cheroot/server.py", line 1277, in communicate
  File "cheroot/server.py", line 710, in parse_request
  File "cheroot/server.py", line 751, in read_request_line
  File "cheroot/server.py", line 301, in readline
  File "_pyio.py", line 574, in readline
  File "_pyio.py", line 553, in nreadahead
  File "_pyio.py", line 1149, in peek
  File "_pyio.py", line 1156, in _peek_unlocked
  File "socket.py", line 706, in readinto
OSError: [Errno 57] Socket is not connected

2023-10-14 23:58:08,101::INFO::[_cplogging:213] [14/Oct/2023:23:58:08] ENGINE Bus STOPPING
2023-10-14 23:58:08,115::INFO::[_cplogging:213] [14/Oct/2023:23:58:08] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 5555)) shut down
2023-10-14 23:58:08,115::INFO::[_cplogging:213] [14/Oct/2023:23:58:08] ENGINE Bus STOPPED
2023-10-14 23:58:08,115::INFO::[_cplogging:213] [14/Oct/2023:23:58:08] ENGINE Bus EXITING
2023-10-14 23:58:08,115::INFO::[_cplogging:213] [14/Oct/2023:23:58:08] ENGINE Bus EXITED
2023-10-14 23:58:08,753::INFO::[_cplogging:213] [14/Oct/2023:23:58:08] ENGINE Bus STARTING
2023-10-14 23:58:08,860::INFO::[_cplogging:213] [14/Oct/2023:23:58:08] ENGINE Serving on http://0.0.0.0:5555
2023-10-14 23:58:08,860::INFO::[_cplogging:213] [14/Oct/2023:23:58:08] ENGINE Bus STARTED
2023-10-14 23:58:37,604::WARNING::[_cplogging:213] [14/Oct/2023:23:58:37] ENGINE socket.error 57
Traceback (most recent call last):
  File "cheroot/server.py", line 1277, in communicate
  File "cheroot/server.py", line 710, in parse_request
  File "cheroot/server.py", line 751, in read_request_line
  File "cheroot/server.py", line 301, in readline
  File "_pyio.py", line 574, in readline
  File "_pyio.py", line 553, in nreadahead
  File "_pyio.py", line 1149, in peek
  File "_pyio.py", line 1156, in _peek_unlocked
  File "socket.py", line 706, in readinto
OSError: [Errno 57] Socket is not connected

2023-10-14 23:58:37,605::WARNING::[_cplogging:213] [14/Oct/2023:23:58:37] ENGINE socket.error 57
Traceback (most recent call last):
  File "cheroot/server.py", line 1277, in communicate
  File "cheroot/server.py", line 710, in parse_request
  File "cheroot/server.py", line 751, in read_request_line
  File "cheroot/server.py", line 301, in readline
  File "_pyio.py", line 574, in readline
  File "_pyio.py", line 553, in nreadahead
  File "_pyio.py", line 1149, in peek
  File "_pyio.py", line 1156, in _peek_unlocked
  File "socket.py", line 706, in readinto
OSError: [Errno 57] Socket is not connected

Edit: Now consistently crashing every few minutes without fail. Way worse than it was.

[safihre]

Unfortunately I can't do much about this. It's something in macOS that's doing it. Or maybe some virusscanner or anti malware service..