Transmission 2.33 All torrents Idle error

[liquidraver]

Dear All!

In the last few days my transmission stopped working.

Altough the client is running perfectly, the remote -l says the torrents are there, but all of them are "Idle"

Seeds and Peers are connected (saw it on the tracker), ports are open, from the syslog&daemon logs: everything is fine, but not a bit is downloaded.

System: latest debian x64

I did not change anything on the system when this error happened, just added a few new torrents to the daemon.

Here is my debug log, I hope anyone can help to track down the error.

Sep 20 16:15:26 transmission-daemon[22371]: Transmission 2.33 (12565) started (session.c:704)
Sep 20 16:15:26 transmission-daemon[22371]: Cache Maximum cache size set to 20.00 MiB (1280 blocks) (cache.c:258)
Sep 20 16:15:26 transmission-daemon[22371]: RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:805)
Sep 20 16:15:26 transmission-daemon[22371]: RPC Server Serving RPC and Web requests on port 127.0.0.1:4042/transmission/ (rpc-server.c:999)
Sep 20 16:15:26 transmission-daemon[22371]: RPC Server Whitelist enabled (rpc-server.c:1003)
Sep 20 16:15:26 transmission-daemon[22371]: Bound socket 13 to port 40170 on 0.0.0.0 (net.c:373)
Sep 20 16:15:26 transmission-daemon[22371]: Bound socket 14 to port 40170 on :: (net.c:373)
Sep 20 16:15:26 transmission-daemon[22371]: Port Forwarding Stopped (port-forwarding.c:181)
Sep 20 16:15:26 transmission-daemon[22371]: Using settings from "/etc/transmission-daemon/" (daemon.c:488)
Sep 20 16:15:26 transmission-daemon[22371]: Saved "/etc/transmission-daemon/settings.json" (bencode.c:1721)
Sep 20 16:15:26 transmission-daemon[22371]: XYZ Read resume file "/etc/transmission-daemon//resume/XYZ.304ca31307033d8d.resume" (resume.c:692)
Sep 20 16:15:26 transmission-daemon[22371]: XYZ Loaded 200 IPv4 peers from resume file (resume.c:140)
Sep 20 16:15:26 transmission-daemon[22371]: XYZ Loaded 19 IPv6 peers from resume file (resume.c:147)
Sep 20 16:15:26 transmission-daemon[22371]: XYZ Resume file found 43 files marked for download (resume.c:205)
Sep 20 16:15:26 transmission-daemon[22371]: Loaded 3 torrents (session.c:1905)
Sep 20 16:15:42 transmission-daemon[22371]: XYZ Announcing to tracker (announcer.c:1484)
Sep 20 16:15:43 transmission-daemon[22371]: XYZ Got 50 peers from tracker (torrent.c:515)
Sep 20 16:15:50 transmission-daemon[22371]: SO_SNDBUF size is 65536 (fdlimit.c:702)
Sep 20 16:15:50 transmission-daemon[22371]: SO_RCVBUF size is 87380 (fdlimit.c:704)
Sep 20 16:21:25 transmission-daemon[22371]: Saved "/etc/transmission-daemon/resume/XYZ.304ca31307033d8d.resume" (bencode.c:1721)

---end of log oO---

[Jordan]

Hi liquidraver,

Thanks for reporting this.

Without knowing more about the swarm, it's hard to know whether or not it makes sense for Transmission to not be downloading.

What I'd like to try first is for the two of us to test things out on the same swarm. Could you pick a torrent from http://www.transmissionbt.com/content/ and see if the behavior persists in its swarm? If so, let me know which torrent you picked and I'll try it out in 2.33.

[liquidraver]

Hi liquidraver

Okay, now that's strange. I worked on this the whole afternoon, and gave up for the day, then I came home, and put a transfer into the daemon, and voilá all of them started. logs still empty...
I installed another client earlier, and the same torrent started in it with no errors, max speed tho.

I'm totally confused, I will post back anything what happens in the next few days. Is there any more debug method I can hook up to the process to log it?

p.s.: is the 70-80% CPU usage is normal for one torrent with 30MB/s download?

[Jordan]

I will post back anything what happens in the next few days. Is there any more debug method I can hook up to the process to log it?

In the hypothetical that there really is a bug in Transmission's code that causes it to not ask for download blocks -- not really.

But my guess is that the problem was an unhealthy swarm.

p.s.: is the 70-80% CPU usage is normal for one torrent with 30MB/s download?

The two biggest CPU sinks in Transmission are (1) running checksums to verify blocks that you download, and (2) the overhead of peer connections being encrypted. These increase in direct relation to download speed, so yes it probably is normal to see a higher load if you're downloading at 30 MB/s. 70-80% still seems high, but that raises the question "70-80% of what?" -- you didn't mention what hardware you're using.

Also, do you see the same CPU load if (for example) you're uploading at the same speed, and have encryption disabled?

[liquidraver]

But my guess is that the problem was an unhealthy swarm.

"70-80% of what?" -- you didn't mention what hardware you're using.

yes sorry :)
/proc/cpuinfo: model name : Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz
/proc/cpuinfo: cpu MHz : 2660.116
/proc/cpuinfo: cache size : 4096 KB

encryption on, no upload

..so that's 70-80%.

unhealthy swarm is not an option, because all other clients on the box and on my windows PC downloading with no error