Hi, I just updated Dietpi with detpi-update command and I’m running 9.15.2.
SABnzbd starts and is accessible in the browser, but when start downloading it looks lke the service crash and I lost the connection to it and no download happens. The rest of the services still work. If I restart the system, it shows up again and crash, the only way to prevent is deleting the download in progress at the moment it starts.
I have reinstalled it but the issue keep going.
Anyone has the same issue?
When I tried to restart the service manually I get this message:
Job for sabnzbd.service failed because a fatal signal was delivered to the control process.
Thanks.
Can you share a log and share required information
#### Required
- DietPi version | `cat /boot/dietpi/.version`
- Distro version | `echo $G_DISTRO_NAME $G_RASPBIAN`
- Kernel version | `uname -a`
- Architecture | `dpkg --print-architecture`
- SBC model | `echo $G_HW_MODEL_NAME` or (EG: RPi3)
Required
DietPi version | cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9G_DIETPI_VERSION_SUB=15G_DIETPI_VERSION_RC=2G_GITBRANCH=‘master’G_GITOWNER=‘MichaIng’
Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
bookworm
Kernel version | uname -a
Linux DietPi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux
Architecture |
amd64
SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
Native PC (x86_64)
I have read in the github of the last release that updates to be prepared for Trixie were in place and it looks SABnzbd is impacted by them.
This has nothing to do with it. You are on Debian Bookworm.
You would need to share some error or log.
Oh ok. that was my guess when I read this: Debian Trixie | Testing and migration script · Issue #7644 · MichaIng/DietPi · GitHub
Now I noticed the log is not working neither, when I try to see it i get:
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/cherrypy/_cprequest.py", line 659, in respond
self._do_respond(path_info)
File "/usr/local/lib/python3.11/dist-packages/cherrypy/_cprequest.py", line 718, in _do_respond
response.body = self.handler()
^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/cherrypy/lib/encoding.py", line 223, in __call__
self.body = self.oldhandler(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/cherrypy/_cpdispatch.py", line 54, in __call__
return self.callable(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/etc/sabnzbd/sabnzbd/interface.py", line 190, in internal_wrap
return wrap_func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/etc/sabnzbd/sabnzbd/interface.py", line 499, in api
return api_handler(kwargs)
^^^^^^^^^^^^^^^^^^^
File "/etc/sabnzbd/sabnzbd/api.py", line 116, in api_handler
response = _api_table.get(mode, (_api_undefined, 2))[0](name, kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/etc/sabnzbd/sabnzbd/api.py", line 670, in _api_showlog
with open(sabnzbd.LOGFILE, "rb") as f:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/etc/sabnzbd/logs/sabnzbd.log'
I started another download and at the moment it failed ran journalctl -u sabnzbd and got a large log but this is the section that shows the error:
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).
Anything before this line? Something is killing the application
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).
not 100% sure but might be an issue with the application. You could try to report to the project GitHub GitHub · Where software is built
I’m having the same problem.
- DietPi version |
cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=15
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
- Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
bookworm
- Kernel version |
uname -a
Linux DietPi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux
- Architecture |
dpkg --print-architecture
amd64
- SBC model |
echo $G_HW_MODEL_NAME or (EG: RPi3)
Native PC (x86_64)
Összefoglaló
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 125.
Aug 03 19:49:57 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 11.
Aug 03 19:49:57 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:49:57 DietPi systemd[1]: sabnzbd.service: Consumed 1.932s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:49:57 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:49:57 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 191 and the job result is done.
Aug 03 19:49:57 DietPi systemd[1]: sabnzbd.service: Consumed 1.932s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:49:57 DietPi systemd[1]: Started sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 191.
Aug 03 19:50:03 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 11.
Aug 03 19:50:03 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:50:03 DietPi systemd[1]: sabnzbd.service: Consumed 2.189s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:50:04 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 2.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:50:04 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 301 and the job result is done.
Aug 03 19:50:04 DietPi systemd[1]: sabnzbd.service: Consumed 2.189s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:50:04 DietPi systemd[1]: Started sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 301.
Aug 03 19:50:08 DietPi SABnzbd[3414]: double free or corruption (!prev)
Aug 03 19:50:08 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 6.
Aug 03 19:50:08 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:50:08 DietPi systemd[1]: sabnzbd.service: Consumed 1.647s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:50:08 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:50:08 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 396 and the job result is done.
Aug 03 19:50:08 DietPi systemd[1]: sabnzbd.service: Consumed 1.647s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:50:08 DietPi systemd[1]: sabnzbd.service: Start request repeated too quickly.
Aug 03 19:50:08 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:50:08 DietPi systemd[1]: Failed to start sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished with a failure.
░░
░░ The job identifier is 396 and the job result is failed.
Aug 03 19:52:02 DietPi systemd[1]: Started sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 477.
Aug 03 19:52:04 DietPi SABnzbd[3928]: double free or corruption (out)
Aug 03 19:52:04 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 6.
Aug 03 19:52:04 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:52:04 DietPi systemd[1]: sabnzbd.service: Consumed 1.157s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:52:04 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:52:04 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 557 and the job result is done.
Aug 03 19:52:04 DietPi systemd[1]: sabnzbd.service: Consumed 1.157s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:52:04 DietPi systemd[1]: Started sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 557.
Aug 03 19:52:06 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 11.
Aug 03 19:52:06 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:52:06 DietPi systemd[1]: sabnzbd.service: Consumed 1.215s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:52:06 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 2.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:52:06 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 637 and the job result is done.
Aug 03 19:52:06 DietPi systemd[1]: sabnzbd.service: Consumed 1.215s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:52:06 DietPi systemd[1]: Started sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 637.
Aug 03 19:52:07 DietPi SABnzbd[4177]: double free or corruption (out)
Aug 03 19:52:07 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 11.
Aug 03 19:52:07 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:52:07 DietPi systemd[1]: sabnzbd.service: Consumed 1.236s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:52:08 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:52:08 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 717 and the job result is done.
Aug 03 19:52:08 DietPi systemd[1]: sabnzbd.service: Consumed 1.236s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:52:08 DietPi systemd[1]: sabnzbd.service: Start request repeated too quickly.
Aug 03 19:52:08 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:52:08 DietPi systemd[1]: Failed to start sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished with a failure.
░░
░░ The job identifier is 717 and the job result is failed.
Aug 03 19:54:24 DietPi systemd[1]: Started sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 797.
Aug 03 19:54:26 DietPi SABnzbd[4615]: free(): double free detected in tcache 2
Aug 03 19:54:26 DietPi SABnzbd[4615]: double free or corruption (!prev)
Aug 03 19:54:26 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 6.
Aug 03 19:54:26 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:54:26 DietPi systemd[1]: sabnzbd.service: Consumed 1.213s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:54:26 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:54:26 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 877 and the job result is done.
Aug 03 19:54:26 DietPi systemd[1]: sabnzbd.service: Consumed 1.213s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:54:26 DietPi systemd[1]: Started sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 877.
Aug 03 19:54:27 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 11.
Aug 03 19:54:27 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:54:27 DietPi systemd[1]: sabnzbd.service: Consumed 1.190s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:54:27 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 2.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:54:27 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 957 and the job result is done.
Aug 03 19:54:27 DietPi systemd[1]: sabnzbd.service: Consumed 1.190s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:54:27 DietPi systemd[1]: Started sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has finished successfully
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished successfully.
░░
░░ The job identifier is 957.
Aug 03 19:54:29 DietPi SABnzbd[4840]: double free or corruption (out)
Aug 03 19:54:29 DietPi systemd[1]: sabnzbd.service: Main process exited, code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ An ExecStart= process belonging to unit sabnzbd.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 6.
Aug 03 19:54:29 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:54:29 DietPi systemd[1]: sabnzbd.service: Consumed 1.400s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:54:29 DietPi systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ Automatic restarting of the unit sabnzbd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 19:54:29 DietPi systemd[1]: Stopped sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A stop job for unit sabnzbd.service has finished
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A stop job for unit sabnzbd.service has finished.
░░
░░ The job identifier is 1037 and the job result is done.
Aug 03 19:54:29 DietPi systemd[1]: sabnzbd.service: Consumed 1.400s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service completed and consumed the indicated resources.
Aug 03 19:54:29 DietPi systemd[1]: sabnzbd.service: Start request repeated too quickly.
Aug 03 19:54:29 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:54:29 DietPi systemd[1]: Failed to start sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished with a failure.
░░
░░ The job identifier is 1037 and the job result is failed.
Aug 03 19:54:39 DietPi systemd[1]: sabnzbd.service: Start request repeated too quickly.
Aug 03 19:54:39 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:54:39 DietPi systemd[1]: Failed to start sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished with a failure.
░░
░░ The job identifier is 1117 and the job result is failed.
Aug 03 19:54:41 DietPi systemd[1]: sabnzbd.service: Start request repeated too quickly.
Aug 03 19:54:41 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:54:41 DietPi systemd[1]: Failed to start sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished with a failure.
░░
░░ The job identifier is 1197 and the job result is failed.
Aug 03 19:54:54 DietPi systemd[1]: sabnzbd.service: Start request repeated too quickly.
Aug 03 19:54:54 DietPi systemd[1]: sabnzbd.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ The unit sabnzbd.service has entered the ‘failed’ state with result ‘signal’.
Aug 03 19:54:54 DietPi systemd[1]: Failed to start sabnzbd.service - SABnzbd (DietPi).
░░ Subject: A start job for unit sabnzbd.service has failed
░░ Defined-By: systemd
░░ Support: Debian Support
░░
░░ A start job for unit sabnzbd.service has finished with a failure.
░░
░░ The job identifier is 1278 and the job result is failed.
Not sure if it is same as the exit code is different one
Per the github, it appears that debian users got a new kernel update (6.1.0-37 - which is kernel 6.1.140) and that is causing the problem. Not Dietpi, not SABznbd.
So, is there a way to downgrade it? Or that is not recommended?
I follow the Sab issue on their GitHub as the discussion is still ongoing. Seems more related to OpenSSL?? Not sure. At least we should wait on the discussion before trying to downgrade the kernel.
Btw: it seems to impact native pc only. Other devices like RPi SBC running different kernel.
There is a workaround provided within the Sab GitHub issue. Hope it’s working until issue has been fixed upstream by OpenSSL guys Crash when start download · Issue #3122 · sabnzbd/sabnzbd · GitHub
1 Like
Thanks!. I would wait. Don’t want to mess with my dietpi setup. Meanwhile I setup as downloader NZBGet, I don’t like it but gets the job done.
Today I noticed after checking apt-get upgrade, that there is an update for openssl. I have applied and so far is working.
