ENGINE socket.error 8 / SABnzbd 4.0.1 [1263068] on a Synology

Report & discuss bugs found in SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
Jr. Member
Jr. Member
Posts: 72
Joined: December 1st, 2019, 2:53 pm

ENGINE socket.error 8 / SABnzbd 4.0.1 [1263068] on a Synology

Post by iUseNetter »

Since the update to the newest available SABnzbd version for a Synology NAS I get this error from time to time:

Code: Select all

WARNING 16 hours ago [21/May/2023:16:01:58] ENGINE socket.error 8
Traceback (most recent call last):
  File "/volume5/@appstore/sabnzbd/env/lib/python3.11/site-packages/cheroot/server.py", line 1287, in communicate
  File "/volume5/@appstore/sabnzbd/env/lib/python3.11/site-packages/cheroot/server.py", line 1077, in respond
  File "/volume5/@appstore/sabnzbd/env/lib/python3.11/site-packages/cheroot/wsgi.py", line 139, in respond
  File "/volume5/@appstore/sabnzbd/env/lib/python3.11/site-packages/cheroot/wsgi.py", line 221, in write
  File "/volume5/@appstore/sabnzbd/env/lib/python3.11/site-packages/cheroot/server.py", line 1133, in write
  File "/volume5/@appstore/sabnzbd/env/lib/python3.11/site-packages/cheroot/makefile.py", line 68, in write
    res = super().write(val, *args, **kwargs)
  File "/volume5/@appstore/sabnzbd/env/lib/python3.11/site-packages/cheroot/makefile.py", line 24, in write
  File "/volume5/@appstore/sabnzbd/env/lib/python3.11/site-packages/cheroot/makefile.py", line 33, in _flush_unlocked
    n = self.raw.write(bytes(self._write_buf))
  File "/var/packages/python311/target/lib/python3.11/socket.py", line 724, in write
    return self._sock.send(b)
  File "/var/packages/python311/target/lib/python3.11/ssl.py", line 1210, in send
    return self._sslobj.write(data)
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2393)
What can I do to solve this problem?

I can't tell you when exactly this error occurs. The last 2 times it was at night, long after the last download was finished.

This ticket seems to describe the problem exactly:
Posts: 4
Joined: August 23rd, 2023, 11:21 am

Re: ENGINE socket.error 8 / SABnzbd 4.0.1 [1263068] on a Synology

Post by das1996 »

Any updates on fixes or work arounds?
Posts: 1
Joined: November 5th, 2023, 10:10 pm

Re: ENGINE socket.error 8 / SABnzbd 4.0.1 [1263068] on a Synology

Post by Vervecine »

That SSL EOF error appears to indicate an issue with the SSL connection being closed unexpectedly while SABnzbd is trying to write data. A few things you could try:

- Upgrade to the latest version of SABnzbd if you haven't already, as newer releases may have fixed similar SSL bugs.

- Try adjusting the SSL/TLS settings in SABnzbd's configurations to use a different protocol like TLS 1.2 or disable outdated ones like SSLv3.

- If using a reverse proxy, check its SSL settings are up to date and secure as well. Outdated protocols can cause issues.

- Make sure the system date/time is accurate. Certificate issues can cause SSL problems.

- Check for firewall, VPN, antivirus or other software that could be interfering with long running SSL connections.

- Monitor system resources in case something is causing the NAS to terminate connections after periods of inactivity.

- Consider running SABnzbd on a different system than the NAS if not directly related to Synology's software.

While tricky to troubleshoot without repro steps, it seems something is causing the SSL socket to timeout or error after being idle. Focus on the SSL configurations and anything that could disrupt connections. Hope this gives you some ideas on where to troubleshoot further!
Post Reply