Transmission 2.33 fails to connect to UDP trackers

Hi I've been running Transmission for a while now with mixed results.

I was running 2.04 with no errors what so ever.

I am now running the 2.34 beta (r4) - this is stable. The only issue I am experiencing is the lack of peers it allows it to connect per torrent. I have mine set to 100 - however, I am seeing around 40 per torrent.

I've been running this for a few weeks. Its not crashed (like some of the earlier releases). I did have some poor trackers - which effected the speed.

Still not getting my full bandwidth but I am assuming this is not related to transmission - more the torrent I am currently downloading.

Happy to post up my working set of params - this was a fresh install after removing 2.04 completely

Devilsrear

Thanks for posting, I'd be interested in your working set. After my last post I tried 2.34, and 2.32 again, but after changing parameters in the settings file they refused to restart. Looking at the forums found others with the same problem but no solution. It's odd because I've never had the problem before... So I got annoyed, removed transmission all together and put bittorrent back on. The Readynas stayed stable - until bittorrent tried to download something, when after a few minutes it disappeared off of the network - the precise reason why I moved to transmission in the first place. So removed that, and was waiting for someone to post a success story before I tried again! So thank you.....

I've noticed the same problem on an NV+ running 4.1.8 with Transmission versions 2.31 and 2.34b04. The one thing I noticed is the data stuck in the receive queue:

readynas:~# netstat -ulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 192.168.1.10:1025       0.0.0.0:*                           1289/minidlna       
udp    64972      0 0.0.0.0:55555           0.0.0.0:*                           4029/transmission-d 
udp        0      0 0.0.0.0:1031            0.0.0.0:*                           4029/transmission-d 
udp        0      0 192.168.1.10:137        0.0.0.0:*                           1500/nmbd           
udp        0      0 0.0.0.0:137             0.0.0.0:*                           1500/nmbd           
udp        0      0 192.168.1.10:138        0.0.0.0:*                           1500/nmbd           
udp        0      0 0.0.0.0:138             0.0.0.0:*                           1500/nmbd           
udp        0      0 0.0.0.0:2190            0.0.0.0:*                           1289/minidlna       
udp        0      0 192.168.1.10:22081      0.0.0.0:*                           1268/raidard        
udp        0      0 0.0.0.0:22081           0.0.0.0:*                           1268/raidard        
udp        0      0 192.168.1.10:50001      0.0.0.0:*                           1281/upnpd          
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           957/avahi-daemon: r 
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1289/minidlna       
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1281/upnpd          
udp        0      0 0.0.0.0:111             0.0.0.0:*                           888/portmap  

Anyone else seeing this? Think it's related to the issue?

yes. i'm having the same issues on my DUO. was on 2.31, went to 2.34b04. stuff downloads but not nearly as fast as it should.

nas-03-C9-69:~# netstat -ulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 192.168.225.5:3073      0.0.0.0:*                           1355/minidlna       
udp        0      0 0.0.0.0:3079            0.0.0.0:*                           1875/transmission-d 
udp        0      0 0.0.0.0:3080            0.0.0.0:*                           1875/transmission-d 
udp        0      0 192.168.225.5:137       0.0.0.0:*                           1825/nmbd           
udp        0      0 0.0.0.0:137             0.0.0.0:*                           1825/nmbd           
udp        0      0 192.168.225.5:138       0.0.0.0:*                           1825/nmbd           
udp        0      0 0.0.0.0:138             0.0.0.0:*                           1825/nmbd           
udp        0      0 0.0.0.0:3083            0.0.0.0:*                           1875/transmission-d 
udp    57540      0 0.0.0.0:36246           0.0.0.0:*                           1875/transmission-d 
udp        0      0 192.168.225.5:22081     0.0.0.0:*                           1335/raidard        
udp        0      0 0.0.0.0:22081           0.0.0.0:*                           1335/raidard        
udp        0      0 192.168.225.5:50001     0.0.0.0:*                           1352/upnpd          
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           880/avahi-daemon: r 
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1355/minidlna       
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1352/upnpd          
udp        0      0 0.0.0.0:111             0.0.0.0:*                           803/portmap         
udp        0      0 239.192.152.143:6771    0.0.0.0:*                           1875/transmission-d 

I have basically the same issue as anyone else. Transmission used to work, now it doesn't. CPU Usage is high (~100%), no DL or UL, lots of message in the Recv-Q, etc ... I've upgraded and downgraded Transmission but no result. I've even bought a new Router (Netgear WNDR3800) to see if that helped but it didn't.

This is my netsstat output:
---
ODDJOB:~# netstat -ulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 192.168.44.168:137 0.0.0.0:* 1600/nmbd
udp 0 0 0.0.0.0:137 0.0.0.0:* 1600/nmbd
udp 0 0 192.168.44.168:138 0.0.0.0:* 1600/nmbd
udp 0 0 0.0.0.0:138 0.0.0.0:* 1600/nmbd
udp 0 0 192.168.44.168:22081 0.0.0.0:* 1344/raidard
udp 0 0 0.0.0.0:22081 0.0.0.0:* 1344/raidard
udp 0 0 192.168.44.168:50001 0.0.0.0:* 1373/upnpd
udp 1048332 0 0.0.0.0:51413 0.0.0.0:* 20138/transmission-
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1110/avahi-daemon:
udp 0 0 0.0.0.0:2666 0.0.0.0:* 20138/transmission-
udp 0 0 0.0.0.0:2667 0.0.0.0:* 20138/transmission-
udp 0 0 0.0.0.0:1900 0.0.0.0:* 1373/upnpd
udp 0 0 0.0.0.0:2669 0.0.0.0:* 20138/transmission-
udp 0 0 0.0.0.0:111 0.0.0.0:* 1053/portmap
---
I've tried different setting in the settings.json file but last time it worked I had the following setting:
---
{
"alt-speed-down": 20480,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 62,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 75,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": true,
"blocklist-url": "http://list.iblocklist.com/?list=bt_level1",
"cache-size-mb": 200,
"dht-enabled": true,
"download-dir": "/media/BitTorrent",
"download-queue-enabled": true,
"download-queue-size": 10,
"encryption": 1,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/media/BitTorrent/_Incomplete",
"incomplete-dir-enabled": true,
"lazy-bitfield-enabled": true,
"lpd-enabled": false,
"max-peers-global": 224,
"max-peers-per-torrent": 60,
"message-level": 2,
"open-file-limit": 32,
"peer-congestion-algorithm": "",
"peer-limit-global": 240,
"peer-limit-per-torrent": 50,
"peer-port": 51413,
"peer-port-random-enabled": 0,
"peer-port-random-high": 65000,
"peer-port-random-low": 48000,
"peer-port-random-on-start": false,
"peer-socket-tos": "default",
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"prefetch-enabled": 0,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"queue-stalled-enabled": true,
"queue-stalled-minutes": 30,
"ratio-limit": 2,
"ratio-limit-enabled": true,
"rename-partial-files": true,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{d15b146a3063b3ade7d0fecaa9602218a327a8c8gOoal64v",
"rpc-port": 8181,
"rpc-url": "/transmission/",
"rpc-username": "admin",
"rpc-whitelist": "*",
"rpc-whitelist-enabled": false,
"scrape-paused-torrents-enabled": true,
"script-torrent-done-enabled": false,
"script-torrent-done-filename": "/c/addons-config/Transmission/email_alert",
"seed-queue-enabled": false,
"seed-queue-size": 10,
"speed-limit-down": 20480,
"speed-limit-down-enabled": false,
"speed-limit-up": 21,
"speed-limit-up-enabled": true,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 0,
"upload-slots-per-torrent": 10,
"utp-enabled": true,
"watch-dir": "/media/BitTorrent/_Sources/",
"watch-dir-enabled": true
}
---

One thing that I have noticed is that before I got problems I usually saw 2 transmission-da processes sharing the ~100% CPU Usage, now I only have one transmission-da process using all the CPU. It does not seem to matter how many concurrent peers I allow or the amount of active Torrents.

For more info: http://www.readynas.com/forum/viewtopic.php?f=36&t=57291

What I would like is to have some better way of getting logs from Transmission, does anybody have any idea on how to get this?

HELP!!! :)

I suspect that the issue is related to https://trac.transmissionbt.com/ticket/4556. Hopefully it will be fixed soon.

ObiWan84 wrote:
I suspect that the issue is related to https://trac.transmissionbt.com/ticket/4556. Hopefully it will be fixed soon.

Thanks ObiWan,

You nailed this one and that explains why it is affecting the SPARC-based models (mine is an NV+). Looks like it was a pretty simple fix. Now we wait for the fix to get packaged and updated here. Thanks for posting.

onryo wrote:
ObiWan84 wrote: I suspect that the issue is related to https://trac.transmissionbt.com/ticket/4556. Hopefully it will be fixed soon. Thanks ObiWan, You nailed this one and that explains why it is affecting the SPARC-based models (mine is an NV+). Looks like it was a pretty simple fix. Now we wait for the fix to get packaged and updated here. Thanks for posting.

Hi,

tested on readynas, and it is not solved.
http://www.readynas.com/forum/viewtopic.php?f=36&p=328290#p328290

I've updated to 2.42 on my ReadyNas Duo, and though Transmission is now stable, it's unable to connect to UDP trackers.

...which is an improvement, it used to just crash.

I upgraded to 2.42 and now have UDP trackers working, but the CPU is sitting at 100% for the transmission-daemon. I can't seem to win for losing with Transmission and the NV+...