SABnzbd Forums

Im running latest version on Mac OS Sonoma, which is always online
its running locally only, listening on a 192.X.X.X address

Usually it will run fine for days without issues but I'm sometimes seeing this error after opening the web client when its been left running a few hours.

Can't think of any reason what could have caused this as there was no disconnects etc during the time of it running

Traceback (most recent call last):
File "cheroot server[dot]py", line 1814, in serve
File "cheroot connections[dot]py", line 198, in run
File "cheroot connections[dot]py", line 252, in _run
File "cheroot connections[dot]py", line 170, in _expire
File "cheroot server[dot]py", line 1360, in close
File "cheroot server[dot]py", line 1480, in _close_kernel_socket
OSError: [Errno 64] Host is down

ive had to replace . with [dot] on the logs above since the forum wasn't allowing the post with it in

Interesting. Guess it's a a race condition when your system is shutdown or in standby.. Not much we can do, it's in one of our depencies.

Its running headless with the only exception being I allow the disks to sleep when idle, possible this is the cause then, will test with them always on

FWIW: the "OSError: [Errno 64] Host is down" is BSD / MacOS specific, meaning:
Instead of disk related, it could be - just a long shot - MacOS cleaning up non-used socket connections, and later on cherrypy fails because of that.


https://man.freebsd.org/cgi/man.cgi?err ... 0is%20down.

seeing this error after opening the web client

Does it happen when you keep the web client open to SABnzbd all the time?

generally its not left open (the web client). sab just runs in the background and I access it from another machine when needed

db18 wrote: ↑January 26th, 2024, 3:00 pm generally its not left open (the web client). sab just runs in the background and I access it from another machine when needed

Exactly. That's why I'm asking you to keep it open. As as test. To see if my hypothesis is correct.