October 20, 201510 yr Hello, Sorry for posting here, but I'm having a general problem, not specific to needo / binhex / linuxserver.io versions of deluge containers, but with deluge itself. I did nothing to change my configuration or update the containers when things stopped working about 1.5 weeks ago. My torrents are not successfully announcing to the tracker, and started looking into if I can actually observe the announces and replies. I figured out how to get into the container, did a tcpdump, and found: 13:13:21.434599 IP (tos 0x0, ttl 64, id 53452, offset 0, flags [DF], proto UDP (17), length 65) acbd263a440b.59039 > 192.168.0.1.domain: [bad udp cksum 0x6d09 -> 0xd04a!] 52588+ A? zzzzzzz.zzzzzzz.zzz. (37) 13:13:21.445184 IP (tos 0x0, ttl 58, id 14344, offset 0, flags [none], proto UDP (17), length 97) 192.168.0.1.domain > acbd263a440b.59039: [udp sum ok] 52588 q: A? zzzzzzz.zzzzzzz.zzz. 2/0/0 zzzzzzz.zzzzzzz.zzz. A yyy.yy.yyy.yy, zzzzzzz.zzzzzzz.zzz. A yyy.yy.yyy.yy (69) where zzzzz represents the tracker's hostname and yyyyyy represents the associated ipaddress. I am able to run another bittorrent client (gfjardim-Transmission) and it works fine. Does anyone have any suggestions on how to debug this? Thank you.
October 20, 201510 yr Author Sorry, the udp cksum error is probably a red herring. This is the name lookup for the (supposedly) following announce. So it looks like no announce is actually going out. I'm comparing to a tcpdump of Transmission, and I see announces going out and replies getting back. I'm still at a loss on how to debug this.
Archived
This topic is now archived and is closed to further replies.