Support Forum

Post the code?

your post too https://github.com/sabnzbd/sabnzbd/issues/3028 ?

It was unrar? That is started by SABnzbd itself. Weird. Although: could still be your virusscanner blocking unrar.

Good it works now again.

download_dir = f:\Download complete_dir = r:\d movies 2025-02-03 15:35:12,753::DEBUG::[filesystem:986] Removing dir recursively f:\Download\A.DOGS.PURPOSE.2017.1080P.BLURAY.DTS-HD 2025-02-03 15:35:12,753::INFO::[filesystem:990] Cannot remove folder f:\Download\A.DOGS.PURPOSE.2017.1080P.BLURAY.DTS-HD...

What do you mean exactly with "nbz clawler"?

If you mean https://www.usenet-crawler.com/ ... what do you get on https://www.usenet-crawler.com/cart ?

safihre wrote: ↑January 30th, 2025, 12:28 pm We can't ignore it. See jcfps comment, this is completely expected behavior to act on it.

I had missed jcfp's post.

Clear.

So ... this hack method seems to work. Can you verify?

We might consider developing an option "ignore_sigterm=1" in sabnzbd.ini so the hacking is not needed. I need the advice from Safihre on that.

Docker: docker run -p 8080:8080 -v /home/sander/docker-sabnzbd-config:/config -v /home/sander/docker-sabnzbd-downloads:/downloads lscr.io/linuxserver/sabnzbd:latest From another terminal: go into the running Docker container docker exec b58140df4bbc -it /bin/bash root@b58140df4bbc:/# cd /app/sabnzbd...

The basics, without Docker: $ sed -i -e 's/signal.SIGTERM, sabnzbd.sig_handler/signal.SIGTERM, signal.SIG_IGN/' SABnzbd.py Check: $ cat SABnzbd.py | grep SIGTERM signal.signal(signal.SIGTERM, signal.SIG_IGN) Good. Starting that SABnzbd.py ... a kill -15 is nicely ignored by SABnzbd. Next step: Docke...

It is what SABnzbd experiences.

I think you have enough knowledge and handles to explore it further.

"1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.00344411 s, 304 MB/s" So the first write is the same speed as SABnzbd experiences it, right? SABnzbd writes a lot of small files (1MB or smaller). "I have mostly the problem that my download is slowed down from the disk, thats why i wondering...

Ah, this is nice, although not useful for you (unless you know how to edit a file within a docker container ... do you know) Start python, and send signal 15 from bash ... terminated: sander@zwarte:~$ python3 Python 3.12.3 (main, Jan 17 2025, 18:03:48) [GCC 13.3.0] on linux Type "help", &q...

Have you googled "signal 15" and "signal 15 sabnzbd"? It's a vague thing because the receiving process (SABnzbd) cannot see which process sent the signal 15. You know it means some other process sent that signal 15 = SIGTERM to SABnzbd? The great thing: with bpftrace -> killsnoop...

Why is it a problem for you? If you go into SABnzbd proxmox VM, what is the output of the command below, but with of pointing to your virtual drive? $ for i in {1..10}; do dd if=/dev/zero of=bla.bin bs=1M count=1 2>&1 | grep MB; done 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.00357261 s, 294 MB/s...