all OLD torrents: Tracker did not respond vs NEW : Success

[ioanonimu]

Since yesterday when I tried to run this command to change the log file:

#transmission-daemon --logfile "/var/log/transmission-daemon.log"

I restarted transmission-daemon and after that I noticed the upload was drastically reduced, I could only see one torrent which was still uploading to some people using the same ISP, all the other torrents ware not uploading anything. All torrents had the tracker status : Tracker did not respond.

If I add a new torrent it seems everything is fine, the status is success and it uploads without any problem, but if I restart transmission i get the same problem with that new torrent also, even if it did not finish downloading the file.

Anyone can give me some suggestions ?

Running centos 5 and transmission 2.12.

[Jordan]

Maybe the old torrents refer to a tracker that's not around anymore?

[ioanonimu]

I mean old by referring to torrents added before the restart of the transmission, the trackers are all up & running, now I see som eactivity on the upload process but the status of the trackers is the same, tracker did not respond.

I have changed one thing now few hours ago, and it seems since than the upload started again, Encryption, from prefered to tolerated, but it was on prefered by default, it did work perfect for one weekn since I install.

In the image attached bellow you can see in the middle of the graph, there ware few hours with very very little traffic, and in the last 8 hours in the graph the traffic started again.

Still I don't know how can I change the log file of transmission, anyone can help me with this ? I want a separated file for transmission log, messages log should be for other stuff.

Thank you.

[ioanonimu]

No one around to help me out, to change the log file of transmission-daemon ?

[rb07]

Running centos 5 and transmission 2.12.

I don't think version 2.12 had the log option. Do you see that option when you run "transmission-daemon -h" ?

[ioanonimu]

I tried now the command you suggested, here is the option :

-e --logfile <filename> Dump the log messages to this filename

How to use it ?

[rb07]

Use it in your start-up script.

One reason why it may not work is if you start the daemon with different users (you mention starting it by hand). Different users have different defaults (the configuration file location if you don't specify it on the parameters), and permissions... so one way it might be able to create/open/write a log file, and with a different user it may not.

[ioanonimu]

here is my startup script, and I start it runing it liek this /etc/init.d/transmission-daemon start being logged in as root, now that I added to the fstab all my CIFS share from the other NAS, I can set up transmission to start up when sistem boots, but the ideea is to run the sistem 24/7, so preferably it will be not to reboot to often.

Code: Select all

#!/bin/bash
#
# chkconfig: - 16 84
# description: Start up transmission-daemon
#
# processname: transmission-daemon
# config: /etc/sysconfig/transmission

# source function library
. /etc/rc.d/init.d/functions

# Get network config
. /etc/sysconfig/network

[ "${NETWORKING}" = "no" ] && exit 0

# Defaults
TRANSMISSION_HOME=/var/lib/transmission

DAEMON_USER="root"
#DAEMON_USER="transmission"
#DAEMON_ARGS="-T --blocklist -g $TRANSMISSION_HOME/.config/transmission"
#DAEMON_ARGS="-T --blocklist "
DAEMON_ARGS=""

# Daemon
NAME=transmission-daemon
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DAEMON=$(which $NAME)
DAEMON_PIDFILE=/var/run/$NAME.pid
DAEMON_LOCKFILE=/var/lock/subsys/$NAME
DAEMON_SCRIPTNAME=/etc/init.d/$NAME
DAEMON_LOGFILE=/var/log/$NAME.log

[ -x "$DAEMON" ] || exit 0
start() {
    echo -n $"Starting ${NAME}: "

    if [ -n "$TRANSMISSION_HOME" ]; then
        export TRANSMISSION_HOME
    fi

    su - $DAEMON_USER -c "$DAEMON $DAEMON_ARGS"

    sleep 2

    status $NAME &> /dev/null && echo_success || echo_failure
    RETVAL=$?

    if [ $RETVAL -eq 0 ]; then
        touch $DAEMON_LOCKFILE
        pidof -o %PPID -x $NAME > $DAEMON_PIDFILE
    fi

    echo
}

stop() {
    echo -n $"Shutting down ${NAME}: "

    killproc $NAME
    RETVAL=$?
[ $RETVAL -eq 0 ] && /bin/rm -f $DAEMON_LOCKFILE $DAEMON_PIDFILE

    echo
}

case "$1" in
    start)
        start
    ;;
    stop)
        stop
    ;;
    restart)
        stop
        start
    ;;
    status)
        status $NAME
    ;;

    *)
        echo "Usage: $SCRIPTNAME {start|stop|restart|status}" >&2
        exit 3
    ;;
esac

I checked again the transmission-daemon.log file and the last message was written in it at 15"45 but now it's 21:57, the messages log has lines from transmission almost every minute

[rb07]

Nice, simple and clean script.

You need to edit DAEMON_ARGS at line 24, you have 2 nice examples above that line, review all the options you want (additional to --logfile) and do a restart.

[kathy]

Hi

'tracker did not respond' with centos can be solved by updating curl in its lastest version and recompiling transmission with correct arguments :

Code: Select all

./configure LIBCURL_CFLAGS=-I/usr/local/include LIBCURL_LIBS="-L/usr/local/lib -lcurl"

Libevent needs to be compiled in its lastest version too.

[Jordan]

I don't know if updating libcurl is a solution or not, but it couldn't hurt.

Newer versions of libcurl definitely seem to more stable than older ones IMO.

[simonpie]

Did the solution of rebuilding transmission with the latest version of libcurl work ?