Open bacontrees opened 1 month ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Issue persists on fresh Debian 12 installation as well.
I'm experiencing this without the VPN. It seems that transmission is becoming a zombie process.
In my k8s cluster, this is preventing the pod from closing. The only way I've found to resolve the issue is to restart the host.
I noticed some log messages in the terminal of the host possibly indicating this: https://github.com/transmission/transmission/issues/1007
I've changed the preallocation
to 0 and have restarted.
Is there an existing issue for this?
Current Behavior
Every few minutes, Transmission reloads with the following logged:
When this happens, download data is frequently corrupted (needs local verify or even says no data found). This system has been running its current configuration for approximately a month without issue and only became problematic recently.
Expected Behavior
Transmission stays alive, does not SIGKILL.
Steps To Reproduce
In Mint 21.3 environment with Docker's official apt repository installed, run Transmission connected to in-service VPN. After a few minutes, s6 kills/restarts Transmission, causing download data corruption (needs local verify or even says no data found).
Environment
CPU architecture
x86-64
Docker creation
Container logs