SABnzbd Forums

I've started experiencing this issue in the last week.

SABnzbd version: 4.5.3 [7a5ca5b]
System: Debian Bookworm Linux 6.12.47+rpt-rpi-v8 aarch64

I have a number of downloads paused in the queue. Within ~ 10 seconds of unpausing the top download, I lose the connection to SAB in the web interface. My Rpi becomes inaccessible via SSH, and I have to power cycle it to get it running again. If I don't resume the download, the system remains up.

The only changes I've made to my system within the relevant timeframe are an update to my DietPi software; the installation of the Recyclarr app; manual installation of zstd.

Should I enable + Debug logging and resume my download? Some other course of action...? Thanks!

EDIT: I did 100MB and 1GB test file downloads, which went off with no issues.

Yes, enable debug logging. You can check the logs without access to the web UI.

But, I suggest starting SABnzbd at the CLI in non-daemon mode. Then you can watch what happens live.

Is this on your Raspi 3?

sander wrote: ↑November 1st, 2025, 2:37 am Is this on your Raspi 3?

sander wrote: ↑November 1st, 2025, 2:37 am Is this on your Raspi 3?

Sorry! Just realized I should've posted this originally in the Debian package support forum.

OneCD wrote: ↑October 31st, 2025, 9:18 pm Yes, enable debug logging. You can check the logs without access to the web UI.

But, I suggest starting SABnzbd at the CLI in non-daemon mode. Then you can watch what happens live.

OK, I set debug logging in the web interface and then did and in the terminal. Went back to the web interface to confirm that debug logging is on. Is that log output written to var/log/sabnzbd?

Also, now that debug logging is on, if I stop the service again and then start in non-daemon mode (just type "sabnzbd" in etc/sabnzbd?), I don't need any flag with that command, since logging is already enabled?

Finally, sabnzbd starts and runs just fine, so long as it's not downloading anything. If I start it via the cli and then resume a download in the web interface, I expect to lose SSH access to my Rpi shortly thereafter. Does that defeat the purpose of watching output at the CLI?

Sorry, I'm new to this process. I appreciate your assistance.

> Finally, sabnzbd starts and runs just fine, so long as it's not downloading anything.

But the 1GB test download went without problems, didn't it?

Options for you:

SSH, sab as service, and "tail -f ~/.sabnzbd/logs/sabnzbd.log". Even if your raspi stops responding, you have the logging.
SSH, sabnzbdplus from command line. Even if your raspi stops responding, you have the logging.
Last resort connect your Raspi 3 to a keyboard and screen. More work, copying the output to this forum more work, but failsafe,

sander wrote: ↑November 2nd, 2025, 5:10 am
But the 1GB test download went without problems, didn't it?

It did. What's more, a couple other files not in my paused queue downloaded without crashing the system. So I tried downloading my paused files one at a time, which worked for a couple of them, but then the system crashed again.

sander wrote: ↑November 2nd, 2025, 5:10 am Options for you:

SSH, sab as service, and "tail -f ~/.sabnzbd/logs/sabnzbd.log". Even if your raspi stops responding, you have the logging.

My sab logs are stored in /var/log/sabnzbd. Does simply starting the service generate debug logging? Becuase I have debug logging set in the web interface, and starting and stopping the service isn't generating any log data in /var/log/sabnzbd.

BTW, since some downloads were completing and others weren't, I enabled full logging on my dietpi box to try to catch an issue as it happened. I didn't see anything obvious in syslog prior to the last issue I had, so I'm really leaning toward some sort of hardware issue. Either SD card, external HD, power supply, or Rpi itself.

https://dietpi.com/forum/t/mysterious-s ... load/24632