It looks like they are in fact the same issue, and the fix provided there has got me back up on my end.
To close the loop for everyone finding this, the issue is known by the sabnzbd team who are working on a fix, temporary solution is to downgrade libssl:
sudo apt-get install libssl3=3.0.16-1~deb12u1
opened 06:09PM - 03 Aug 25 UTC
Bug
### SABnzbd version
4.5.2 [bae5563]
### Operating system
Debian - Bookworm
… ### Using Docker image
None
### Description
Hi,
I;m getting the following error log, but basically, when it start a download it crash.
[quote="rafa1138, post:7, topic:23908"]
```
Aug 03 15:42:48 DietPi SABnzbd[136141]: 2025-08-03 15:42:48,772::INFO::[newswrapper:351] 3@news.newshosting.com: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
Aug 03 15:42:48 DietPi SABnzbd[136141]: 2025-08-03 15:42:48,774::INFO::[newswrapper:351] 41@news.newshosting.com: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
Aug 03 15:42:48 DietPi SABnzbd[136141]: 2025-08-03 15:42:48,774::INFO::[newswrapper:351] 16@news.newshosting.com: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
Aug 03 15:42:48 DietPi SABnzbd[136141]: malloc(): unsorted double linked list corrupted
Aug 03 15:42:48 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=6/ABRT
Aug 03 15:42:48 DietPi systemd[1]: sabnzbd.service: Failed with result 'signal'.
Aug 03 15:42:48 DietPi systemd[1]: sabnzbd.service: Consumed 1.465s CPU time.
Aug 03 15:42:49 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 7.
Aug 03 15:42:49 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
Aug 03 15:42:49 DietPi systemd[1]: sabnzbd.service: Consumed 1.465s CPU time.
Aug 03 15:42:49 DietPi systemd[1]: sabnzbd.service: Start request repeated too quickly.
Aug 03 15:42:49 DietPi systemd[1]: sabnzbd.service: Failed with result 'signal'.
Aug 03 15:42:49 DietPi systemd[1]: Failed to start sabnzbd.service - SABnzbd (DietPi).
```
[/quote]
I have SABnzbd running in Debian with Dietpi.
1 Like