Won't download public tracker torrents?

General support for problems installing or using Deluge
Post Reply
kvadevack
New User
New User
Posts: 2
Joined: Sat Jul 24, 2021 2:37 pm

Won't download public tracker torrents?

Post by kvadevack »

Private tracker torrents work fine, but e.g. the Ubuntu torrent gets stuck at "Downloading 0.00%" with the following errors:

Code: Select all

tracker_announce_alert: ubuntu-20.04.2-live-server-amd64.iso (https://torrent.ubuntu.com/announce) sending announce (started)
tracker_error_alert: ubuntu-20.04.2-live-server-amd64.iso (https://torrent.ubuntu.com/announce) (-1) Connection timed out "" (1)
tracker_announce_alert: ubuntu-20.04.2-live-server-amd64.iso (https://ipv6.torrent.ubuntu.com/announce) sending announce (started)
tracker_error_alert: ubuntu-20.04.2-live-server-amd64.iso (https://ipv6.torrent.ubuntu.com/announce) (-1) Address family not supported by protocol "" (1)
Tracker Error Alert: ubuntu-20.04.2-live-server-amd64.iso (https://torrent.ubuntu.com/announce) (-1) Connection timed out "" (1) [Connection timed out]
Tracker Error Alert: ubuntu-20.04.2-live-server-amd64.iso (https://ipv6.torrent.ubuntu.com/announce) (-1) Address family not supported by protocol "" (1) [Address family not supported by protocol]
Deluge is running in a container on Kubernetes, and I've verified with tcpdump that both TCP and UDP traffic on port 6881 can reach it, and that the container has Internet access. I've also verified that the torrent can be downloaded with another client from the host.
I've observed that Deluge doesn't listen on TCP Port 6881, despite claiming so in the logs. Only UDP. Normal?

Code: Select all

listen_succeeded_alert: successfully listening on [TCP] [::]:6881
listen_succeeded_alert: successfully listening on [TCP] 0.0.0.0:6881
listen_succeeded_alert: successfully listening on [UDP] 0.0.0.0:6881
log_alert: >>> SET_TOS [ udp_socket tos: 20 e: Bad file descriptor ]
portmap_log_alert: UPnP: adding port map: [ protocol: tcp ext_port: 6881 local_ep: 0.0.0.0:6881 ] 
log_alert: update listen interfaces: 0.0.0.0:68810.0.0.0:68820.0.0.0:68830.0.0.0:68840.0.0.0:68850.0.0.0:68860.0.0.0:68870.0.0.0:68880.0.0.0:68890.0.0.0:68900.0.0.0:6891
log_alert: failed to treat 0.0.0.0:68810.0.0.0:68820.0.0.0:68830.0.0.0:68840.0.0.0:68850.0.0.0:68860.0.0.0:68870.0.0.0:68880.0.0.0:68890.0.0.0:68900.0.0.0 as an IP address [ Invalid argument ]
log_alert: failed to find device 0.0.0.0:68810.0.0.0:68820.0.0.0:68830.0.0.0:68840.0.0.0:68850.0.0.0:68860.0.0.0:68870.0.0.0:68880.0.0.0:68890.0.0.0:68900.0.0.0
performance_alert:  - : performance warning: using bittyrant unchoker with no upload rate limit set
Handling alert: performance_alert
log_alert: >>> SET_TOS [ udp_socket tos: 0 e: Bad file descriptor ]
udp_error_alert: UDP error: Bad file descriptor from: 0.0.0.0
listen_failed_alert: listening on 0.0.0.0:68810.0.0.0:68820.0.0.0:68830.0.0.0:68840.0.0.0:68850.0.0.0:68860.0.0.0:68870.0.0.0:68880.0.0.0:68890.0.0.0:68900.0.0.0 : 0.0.0.0:6891 failed: [open] [TCP] No such device
Extended logs: https://pastebin.com/WGnLfNNK
mhertz
Moderator
Moderator
Posts: 2195
Joined: Wed Jan 22, 2014 5:05 am
Location: Denmark

Re: Won't download public tracker torrents?

Post by mhertz »

Not sure, but seemingly you're atleast hit by a bug fixed in develop branch, about sending the bound ip/port to libtorrent wrong, missing commas, so if possible I'd apply said commit, which just is one added char, and then retry, but honestly don't get why not working only for public torrents.

https://github.com/deluge-torrent/delug ... a3b269fb95

The message about address family not supported, I quickly read up upon and saw a libtorrent ticket where there was this error because of IPv6 not supported/enabled, and libtorrent tried it still, and Arvid lead-dev stated workaround to add your interface IP to bind-interface, or you could use name, eth0 or whatever, worth a shoot, and you use libtorrent 1.1.x, which uses IPv6 also by default, through 0.0.0.0, in contrary to libtorrent 1.2.x. Also I'm not sure if was same message, but I remember getting somewhat related error once when testing a libtorrent built without crypto=openssl, which made https announces time out/fail, though would be strange to build libtorrent without that, but just throwing out there anyway, and as message was about https url - if openssl missing would be same, but normally wouldn't neither, I'm thinking.

Sorry don't know the answer better, and hopefully others in the know can be more helpful, but maybe try in meantime if applying the fix for listening interfaces manually helps, and if still issue try bind in/out to own IP/interface_name.
kvadevack
New User
New User
Posts: 2
Joined: Sat Jul 24, 2021 2:37 pm

Re: Won't download public tracker torrents?

Post by kvadevack »

Thanks for your reply, really appreciated! Don't know why it didn't strike me to try, but I built the develop branch and the issue went away.
Post Reply