memory leaking? about docker-transmission HOT 14 CLOSED

@dedmo, are you using an blocklist? If so, my bet: https://github.com/linuxserver/docker-transmission/blob/master/root/defaults/blocklist-update.sh

@thelamer thoughts?

from docker-transmission.

@jkaberg, Yes I'm use blocklist. Sorry, can't comment script, I'm simple user :-|
Since 3 Jul i'm test linuxserver/transmission with disabled UDP. It looks like the RAM usage has decreased. Please see attached screenshot with total system RAM usage for last month.

But additional background process "transmission-daemon" continues to be added. Jul 3 - 1 process "transmission-daemon", today 5 Jul - 4 process.

from docker-transmission.

@dedmo Unless I read this completely wrong the blocklist script will launch a new instance of transmission each time its run (which is everyday according to the README)

Interesting take on UDP, will keep that in mind

from docker-transmission.

Based on the Transmission documentation the blocklist script should do something like this instead:

SID=$(curl -sSLI http://localhost:9091/transmission/ | grep -Fi X-Transmission-Session-Id | cut -d ' ' -f 2) curl -sSL http://localhost:9091/transmission/rpc -H "X-Transmission-Session-Id: $SID" -d '{\"method\":\"blocklist-update\",\"arguments\":{},\"tag\":\"\"}'

The above is not tested. This should replace the current restart method as thats unnecessary.

from docker-transmission.

@jkaberg
Thanks for your time. Now I set "blocklist-enabled": false. I'm check it after few days and leave a comment here (if needed).
Do I understand correctly that sometime in the next versions the blocklist script may be fixed?

from docker-transmission.

@jkaberg that doesn't take into account that someone may be using a password

from docker-transmission.

@sparklyballs just parse the settings.json file?

Psuedo code - untested:

#!/usr/bin/bash
USER=$(cat /config/settings.json | jq .\"rpc-user\")
PASSWORD=$(cat /config/settings.json | jq .\"rpc-password\")

if [ -z "$PASSWORD" ] then
    SID=$(curl -sSLI http://localhost:9091/transmission/ | grep -Fi X-Transmission-Session-Id | cut -d ' ' -f 2)
else
    SID=$(curl -sSLI -u "$USER":"$PASSWORD" http://localhost:9091/transmission/ | grep -Fi X-Transmission-Session-Id | cut -d ' ' -f 2)
fi

curl -sSL http://localhost:9091/transmission/rpc -H "X-Transmission-Session-Id: $SID" -d '{\"method\":\"blocklist-update\",\"arguments\":{},\"tag\":\"\"}'

from docker-transmission.

@jkaberg
Thanks for your time. Now I set "blocklist-enabled": false. I'm check it after few days and leave a comment here (if needed).

In my case (after testing):

1. utp-enabled: false - normalize RAM use and system
2. blocklist-enabled: false - background process "transmission-daemo" no longer multiplies each days

from docker-transmission.

Closing pending #78

from docker-transmission.

Unfortunatelly multiply pocess issue not solved. See screenshot below (latest version linuxserver/transmission)

from docker-transmission.

@dedmo post logs and also execute into the container and run :

s6-svc -t /var/run/s6/services/transmission

This is the output you should get:

Caught SIGTERM signal!
localhost:9091/transmission/rpc/ responded: "success"
[2019-07-22 16:18:58.850] Saved "/config/settings.json" (variant.c:1266)
[2019-07-22 16:18:58.850] DHT Not saving nodes, DHT not ready (tr-dht.c:359)
[2019-07-22 16:18:58.850] Port Forwarding Stopped (port-forwarding.c:180)
Closing transmission session... done.

Then s6 will pickup and start the app as it detects the down pid.

from docker-transmission.

NM I see what is wrong, you need to delete the existing blocklis-update script in /config and restart the container.
https://github.com/linuxserver/docker-transmission/blob/master/root/etc/cont-init.d/20-config#L11-L13

The assumption is that people are customizing this script.

from docker-transmission.

@thelamer
log file attached.
linuxserver-transmission2.zip

I deleted "blocklist-update.sh" in "/config" and restarted container. I will return with the result in a few days. Thanks.

from docker-transmission.

NM I see what is wrong, you need to delete the existing blocklis-update script in /config and restart the container.
https://github.com/linuxserver/docker-transmission/blob/master/root/etc/cont-init.d/20-config#L11-L13

The assumption is that people are customizing this script.

Unfortunatylly steps:

• stop container
• delete "blocklist-update.sh" in "/config"
• run contaiter
  don't solve problem - process "transmission-daemon" still multiply.
  

from docker-transmission.