Transmission 2.12 Web GUI crashing

[acidrain]

Hello,

I am running Transmission 2.12 on My World Book II (white light) edition. It was installed via Optware.

I have no trouble adding torrents, the problem is with the web browser open (I.E / Safari / Firefox - all the same) to server:9091 the web gui is displayed, for a while. Eventually you get "Connection Failed. Could not connect to the server. You may need to reload the page to reconnect.".

Doing a refresh sometimes works, but eventually (even if you restart transmission via killall transmission-daemon, transmission-daemon) the web page will no longer load. It hangs loading with a blank page and the only way around it is to restart transmission, it when it will just happen again from within a short amount of time.

It is very frustrating and I open open to suggestions on how to stablish the web gui - also out of interest, when the web gui crashes, are the torrents still d/l in the background? Is their an ssh command line that can be run to see this information?

Thanks.

[ntompson]

Hi Acidrain,

I am having the same problem (I think). I have been having it for quite some versions now. I also have the white light MyBook. I have also installed transmission by Optware, and have upgraded as new versions come to hand.

I find that, after some completely random length of time - sometimes 20 minutes, sometimes many hours, the transmission web GUI stops responding. After some investigation, it has become clear to me that this is not a GUI problem, but with the transmission-daemon itself. "transmission-remote -si" also returns nothing at the same point. I have also installed MRTG to monitor both my router and the MyBook; it also shows that network activity drops to zero when this happens. So I think it is safe to conclude that UL / DL stops when this happens.

Like you, I have to kill and restart the transmission-daemon process to get things going again.

The annoying thing is that there are absolutely no error messages to help. Transmission-daemon reports into the system message log regularly, but there are no unusual messages prior to this happening. There are no dump files, nothing useful that I can find at all. I have tried running transmission-daemon in the foreground, but this also yields nothing interesting other than what I already see in the system log. I've also tried verbose logging, but it yields so much stuff that it is almost impossible to see what is going on.

There also seems to be no correlation with anything i do in terms of adding / removing torrents, other than a vague impression that it is associated with heavier torrent activity. Note that I have limited the max number of torrents to 20; while this seems to have increased the time it takes to crash, it still crashes. Note also that it never crashes if there are no open torrents.

I have googled plenty on this; I have found nothing. Which I guess is not surprising, given that I have no error messages to search on. I'd be very interested if others are seeing similar symptoms, or if anyone has suggestions on how to deal with this.

Nick

[ntompson]

Sorry - typo on my part. I have limited max peers to 20, not max torrents. I figure this is a very conservative setting.

[zeppelin]

Hi Acidrain,

I am having the same problem (I think). I have been having it for quite some versions now. I also have the white light MyBook. I have also installed transmission by Optware, and have upgraded as new versions come to hand.

I find that, after some completely random length of time - sometimes 20 minutes, sometimes many hours, the transmission web GUI stops responding. After some investigation, it has become clear to me that this is not a GUI problem, but with the transmission-daemon itself. "transmission-remote -si" also returns nothing at the same point. I have also installed MRTG to monitor both my router and the MyBook; it also shows that network activity drops to zero when this happens. So I think it is safe to conclude that UL / DL stops when this happens.

Like you, I have to kill and restart the transmission-daemon process to get things going again.

The annoying thing is that there are absolutely no error messages to help. Transmission-daemon reports into the system message log regularly, but there are no unusual messages prior to this happening. There are no dump files, nothing useful that I can find at all. I have tried running transmission-daemon in the foreground, but this also yields nothing interesting other than what I already see in the system log. I've also tried verbose logging, but it yields so much stuff that it is almost impossible to see what is going on.

There also seems to be no correlation with anything i do in terms of adding / removing torrents, other than a vague impression that it is associated with heavier torrent activity. Note that I have limited the max number of torrents to 20; while this seems to have increased the time it takes to crash, it still crashes. Note also that it never crashes if there are no open torrents.

I have googled plenty on this; I have found nothing. Which I guess is not surprising, given that I have no error messages to search on. I'd be very interested if others are seeing similar symptoms, or if anyone has suggestions on how to deal with this.

Nick

I am having the same problem. I dont thing that this has to do with the number of connections connections.
edit: In fact it crashes even if no torrent is loaded.

[rb07]

I am having the same problem. I dont thing that this has to do with the number of connections connections.
edit: In fact it crashes even if no torrent is loaded.

You are correct. In fact it is a well known problem that affects many NASes, it went away long time ago (with new versions of Transmission or libevent) but some NASes still have the problem.

Anyway the solution is to disable libevent's use of epoll, just before you start the daemon set the environment variable :

Code: Select all

EVENT_NOEPOLL=1; export EVENT_NOEPOLL

[acidrain]

Thanks rb07. This seems to have resolved the issue. It still occurred after upgrading to 2.13, then I tried your fix and it has not crashed yet.

ntompson - how did you get on with this?

[rb07]

It still occurred after upgrading to 2.13

Let me be clear, it is not a Transmission bug, changing Transmission settings or versions will not solve anything.

I just mentioned that the problem seemed to be solved after changing libevent and T versions over time, in fact in my NAS I haven't seen this problem in probably a year or more, but there was another problem also related to epoll (I'm not sure if the real bug is in the kernel or in libc) so I put the disable back again.

[lakrigg]

simple way to make this work on startup.

Edit your /opt/etc/init.d transmission script and add

this is my S90transmission file


#!/bin/sh

prefix="/opt"

PATH=${prefix}/bin:${prefix}/sbin:/sbin:/bin:/usr/sbin:/usr/bin
NAME=transmission-daemon
CONFIGDIR=/root/.config/transmission-daemon
DAEMON=${prefix}/bin/${NAME}

test -x $DAEMON || exit 0

if [ -z "$1" ] ; then
case `echo "$0" | sed 's:^.*/\(.*\):\1:g'` in
S??*) rc="start" ;;
K??*) rc="stop" ;;
*) rc="usage" ;;
esac
else
rc="$1"
fi

case "$rc" in
start)
echo "Starting Torrent client: $NAME"
EVENT_NOEPOLL='0' nice $DAEMON -g ${CONFIGDIR}
;;
stop)
#if [ -n "`pidof $NAME`" ]; then
echo "Stopping Torrent client: $NAME"
killall $NAME 2> /dev/null
#fi
;;
restart)
"$0" stop
sleep 1
"$0" start
;;
*)
echo "Usage: $0 (start|stop|restart|usage)"
;;
esac

exit 0




See above, add the prefix before nice to autostart

[hades_6_6_6]

Hi,
I've got exactly the same problem. Network breaking down after a while.
Unfortunately, the "EVENT_NOEPOLL='0'" didn't help. Probably because I am not using a NAS.
Transmission is installed on a DREAMBOX DM500HD sat receiver with a eSATA attached external HD.
I cannot imagine, that is a NAS related issue.

[rb07]

Hi,
I've got exactly the same problem. Network breaking down after a while.
Unfortunately, the "EVENT_NOEPOLL='0'" didn't help. Probably because I am not using a NAS.
Transmission is installed on a DREAMBOX DM500HD sat receiver with a eSATA attached external HD.
I cannot imagine, that is a NAS related issue.

With version 2.12?

With the wrong value? (Its EVENT_NOEPOLL=1).

And it doesn't have to be a NAS, any Linux based device with crappy old libc and kernel... which just happens to be most of the NASes.

[darjon]

Everything working fine for me with the new version, all issues have been solved me thinks.