Transmission server hangs

[fredjsquirrel]

I've been using the Transmission Daemon for a couple of weeks now and it has been running fine.

However, I tried to connect to it today (using both the GUI Transmission Remote on Windows XP and Command Line Transmission-Remote on the server) and I'm getting a time out.

I tried to stop and restart the Daemon on the server and I have to do a killall -9 transmission-daemon to get it to stop. I tried running the daemon in the foreground and without any other parameters, it seems to be ok, but as soon as I run it with the config file it hangs. I can't even ctrl-c out of it in FG mode.

I'm running Transmission on a D-Link DNS-323 NAS Device if the Funplug installed.
Transmission version is: 1.74
My config file is:

{
"alt-speed-down": 50,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "",
"blocklist-enabled": false,
"dht-enabled": true,
"download-dir": "/mnt/HD_a2/Media/Downloads",
"encryption": 1,
"lazy-bitfield-enabled": true,
"message-level": 2,
"open-file-limit": 32,
"peer-limit-global": 50,
"peer-limit-per-torrent": 60,
"peer-port": 51413,
"peer-port-random-high": 65535,
"peer-port-random-low": 49152,
"peer-port-random-on-start": false,
"peer-socket-tos": 0,
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2.0000,
"ratio-limit-enabled": true,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{f25c10da3479425322494e367151a524e3ce89787gMtdqUK",
"rpc-port": 9091,
"rpc-username": "root",
"rpc-whitelist": "127.0.0.1,192.168.*.*",
"rpc-whitelist-enabled": true,
"speed-limit-down": 200,
"speed-limit-down-enabled": true,
"speed-limit-up": 50,
"speed-limit-up-enabled": true,
"umask": 18,
"upload-slots-per-torrent": 14
}

Any ideas what I might have wrong?


Thanks in Advance.

[ukoda]

I am seeing exactly the same problem after the reboot of what has been a reliable set up for several weeks. I wonder if there is an external factor. The only thing of significance here is we have entered daylight savings yesterday. I was 9 minutes away from completing a 27GB download and I have a couple of similar size downloads in the pipe so I guess it could take a long time to check them at startup but I can't say I have had any issues with restarting in the past with large downloads in progress.

[ukoda]

Mine is now working ok after leaving running for an hour or so I'm guessing it was unresponsive while checking the state of the downloads in progress. I haven't had that problem before so maybe it the shutdown had not gone as cleanly as in the past.

[fredjsquirrel]

Ok, mine has been running for almost 24 hours now and it hasn't cleared itself up.

However, I guess it could be something to do with the torrents it is currently working on. I'll move those somewhere else and see if that works.

[rb07]

I've seen something similar, but you guys describe many things:

- Changing system time (daylight savings is one way) makes the daemon go crazy with the stats and speeds.

- Restarting the daemon makes it unresponsive for a while... this only happens with the latest version, 1.75 for sure, 1.74 maybe (I don't restart the daemon often but it may have happened when I changed versions, I just don't recall). Weird thing is that the daemon is unresponsive to transmission-remote but it does reply on the Web client.

- Daemon unresponsive for a long time, nope, I haven't seen that. It does behave very different depending on the number of torrent you have active, and it doesn't show in CPU or RAM use, it just works erratically... it may be a simple problem with the limit of connections, I haven't changed the default (260?) and I would expect at some point it runs out of available connections or it starts changing connections from one torrent to another... I haven't investigated further since I usually have just around a dozen torrents, but I saw problems when I increased to 3 dozen (and this is in a powerful server, in my NAS I try not to have more than 4 active torrents or everything takes forever). You could see if the problem is the number of torrent by starting the daemon with the new "paused" option (meaning: all torrents paused)... oh yes, the latest version also brought the annoying "feature" of starting with whatever it wants active (making paused torrent active for no good reason -- oh well, you get what you paid for).

No real solution here people, move on.

[fredjsquirrel]

Ok, it must have something to do with the number of clients or just something taking way to long or some such like that.

I just tried connecting (after ignoring it for a few days) and I can now access it.

So I guess I'll take that as a don't over load the system and limit what I'm downloading at any one time.

Thanks for the help. At least I know I'm not alone on this one.

As for getting what you pay for. Very true, and I am in fact very pleased with what I've seen with Transmission so far. So no complaints. Besides, if I have an actually "beef" with the way the system works, then I can just get off my lazy butt offer to figure out the problem and fix it. Simple as that.