Won't download public tracker torrents?
Posted: Sat Jul 24, 2021 8:17 pm
Private tracker torrents work fine, but e.g. the Ubuntu torrent gets stuck at "Downloading 0.00%" with the following errors:
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?
Extended logs: https://pastebin.com/WGnLfNNK
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]
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