Why are rarely any torrent seeders available for downloading the ISO?

xerus · 2023-06-17 13:21:26

I would prefer to download the ISO via torrent, but in KTorrent I barely ever see a seeder (or leecher, for that matter).
If a torrent is provided I would expect at least a few of the mirrors to automatically act as initial seeders. In the long term this could easily balance the load of the mirrors.
Otherwise we have a hen-egg problem where leechers do not find seeders and thus rarely become seeders themselves.

Lone_Wolf · 2023-06-17 15:24:33

transmission-cli has no problem finding seeders . Most are discovered through DHT .

Do you have DHT enabled in ktorrent ?

iznobe · 2023-06-18 09:28:39

hi , i have downloaded the .ISO file archlinux-2023.06.01-x86_64.iso without any problem using transmission-gtk in less than 10 minutes with 20 MB/s bandwith .

try transmission .

nl6720 · 2023-06-18 11:28:32

The 2023.06.01 ISO torrent has 354 web seeds. You need to download the torrent file instead of using the magnet link to get them, though.

AFAIK the only BitTorrent client that may have issues with Arch torrents is rtorrent since it needs configuring to enable DHT.

ugjka · 2023-06-18 11:34:34

i would recommend using transmission-qt

nl6720 · 2023-06-18 11:39:03

Any client works as long as it the meets the requirements:

https://archlinux.org/download/ wrote:

A DHT capable client is required. A WebSeed capable client is recommended for fastest download speeds.

Since we're all advertising our favorite torrent clients, my vote's for qBittorrent.

xerus · 2024-06-10 06:53:57

I am still using KTorrent, with DHT enabled, and encounter this issue.

Transmission is not faring any better:
```sh
❯ transmission-cli archlinux-2024.06.01-x86_64.iso.torrent
transmission-cli 4.0.5 (a6fe2a64aa)
[2024-06-10 09:52:57.351] web.cc:174: Will verify tracker certs using envvar CURL_CA_BUNDLE: none
[2024-06-10 09:52:57.351] web.cc:176: NB: this only works if you built against libcurl with openssl or gnutls, NOT nss
[2024-06-10 09:52:57.351] web.cc:177: NB: Invalid certs will appear as 'Could not connect to tracker' like many other errors
[2024-06-10 09:52:57.351] rpc-server.cc:763: Added '127.0.0.1' to host whitelist
[2024-06-10 09:52:57.351] rpc-server.cc:763: Added '::1' to host whitelist
[2024-06-10 09:52:57.351] rpc-server.cc:923: Serving RPC and Web requests from '/usr/share/transmission/public_html'
[2024-06-10 09:52:57.352] session.cc:646: Transmission version 4.0.5 (a6fe2a64aa) starting
[2024-06-10 09:52:57.352] session.cc:404: Listening to incoming peer connections on [0.0.0.0]:51413
[2024-06-10 09:52:57.352] session.cc:404: Listening to incoming peer connections on [::]:51413
[2024-06-10 09:52:57.352] port-forwarding.cc:215: State changed from 'Not forwarded' to 'Starting'
[2024-06-10 09:52:57.352] tr-udp.cc:168: Bound UDP IPv4 address [0.0.0.0]:51413
[2024-06-10 09:52:57.352] tr-udp.cc:202: Bound UDP IPv6 address [::]:51413
[2024-06-10 09:52:57.453] rpc-server.cc:763: Added '127.0.0.1' to host whitelist
[2024-06-10 09:52:57.453] rpc-server.cc:763: Added '::1' to host whitelist
[2024-06-10 09:52:57.453] rpc-server.cc:923: Serving RPC and Web requests from '/usr/share/transmission/public_html'
Progress: 0.0%, dl fro[2024-06-10 09:53:03.554] web.cc:447: Couldn't fetch 'https://arch.kurdy.org/iso/2024.06.01/a … x86_64.iso': expected HTTP response code 206, got 200
[2024-06-10 09:53:03.738] web.cc:447: Couldn't fetch 'https://arch.kurdy.org/iso/2024.06.01/a … x86_64.iso': expected HTTP response code 206, got 200
[2024-06-10 09:53:04.655] web.cc:447: Couldn't fetch 'https://arch.kurdy.org/iso/2024.06.01/a … x86_64.iso': expected HTTP response code 206, got 200
[2024-06-10 09:53:04.966] web.cc:447: Couldn't fetch 'https://arch.kurdy.org/iso/2024.06.01/a … x86_64.iso': expected HTTP response code 206, got 200
Progress: 0.0%, dl from 0 of 0 peers (91 kB/s), ul to 0 (0 kB/s) [0.00] [2024-06-10 09:53:05.088] port-forwarding.cc:215: State changed from 'Starting' to '???'
[2024-06-10 09:53:05.179] web.cc:447: Couldn't fetch 'https://kacabenggala.uny.ac.id/archlinu … x86_64.iso': expected HTTP response code 206, got 404
[2024-06-10 09:53:05.203] web.cc:447: Couldn't fetch 'https://kacabenggala.uny.ac.id/archlinu … x86_64.iso': expected HTTP response code 206, got 404
[2024-06-10 09:53:06.193] web.cc:447: Couldn't fetch 'https://mirror.lebedinets.ru/archlinux/ … x86_64.iso': expected HTTP response code 206, got 403
[2024-06-10 09:53:06.743] web.cc:447: Couldn't fetch 'https://mirror.lebedinets.ru/archlinux/ … x86_64.iso': expected HTTP response code 206, got 403
[2024-06-10 09:53:07.073] web.cc:447: Couldn't fetch 'https://mirror.the-repo.org/ArchMirror/ … x86_64.iso': expected HTTP response code 206, got 403
Progress: 0.0%, dl from 0 of 0 peers (553 kB/[2024-06-10 09:53:07.963] web.cc:447: Couldn't fetch 'https://mirrors.opensource.is/archlinux … x86_64.iso': expected HTTP response code 206, got 404
[2024-06-10 09:53:09.073] web.cc:447: Couldn't fetch 'https://mirrors.opensource.is/archlinux … x86_64.iso': expected HTTP response code 206, got 404
[2024-06-10 09:53:10.124] web.cc:447: Couldn't fetch 'https://mirrors.opensource.is/archlinux … x86_64.iso': expected HTTP response code 206, got 404
Progress: 0.0%, [2024-06-10 09:53:11.303] web.cc:447: Couldn't fetch 'https://mirror.jordanrey.me/archlinux/i … x86_64.iso': expected HTTP response code 206, got 403
Progress: 0.0%, dl from 0 of 0 peers (738 kB/s), ul to 0 (0 kB/s) [0[2024-06-10 09:53:12.734] web.cc:447: Couldn't fetch 'https://mirror.the-repo.org/ArchMirror/ … x86_64.iso': expected HTTP response code 206, got 403
[2024-06-10 09:53:13.162] web.cc:447: Couldn't fetch 'https://mirrors.opensource.is/archlinux … x86_64.iso': expected HTTP response code 206, got 404
[2024-06-10 09:53:14.281] web.cc:447: Couldn't fetch 'https://mirror.jordanrey.me/archlinux/i … x86_64.iso': expected HTTP response code 206, got 403
Progress: 0.0%, dl from 0 of 0 peers (5[2024-06-10 09:53:15.579] web.cc:447: Couldn't fetch 'https://mirror.the-repo.org/ArchMirror/ … x86_64.iso': expected HTTP response code 206, got 403
[2024-06-10 09:53:16.436] web.cc:447: Couldn't fetch 'https://mirror.worldhotspot.org/archlin … x86_64.iso': expected HTTP response code 206, got 404
[2024-06-10 09:53:16.552] web.cc:447: Couldn't fetch 'https://mirror.metanet.ch/archlinux/iso … x86_64.iso': expected HTTP response code 206, got 404
[2024-06-10 09:53:17.245] web.cc:447: Couldn't fetch 'https://mirror.metanet.ch/archlinux/iso … x86_64.iso': expected HTTP response code 206, got 404
Progress: [2024-06-10 09:53:18.779] web.cc:447: Couldn't fetch 'https://mirror.worldhotspot.org/archlin … x86_64.iso': expected HTTP response code 206, got 404
Progress: 0.0%, dl from 0 of 0 pe[2024-06-10 09:53:24.661] web.cc:447: Couldn't fetch 'https://kacabenggala.uny.ac.id/archlinu … x86_64.iso': expected HTTP response code 206, got 404
[2024-06-10 09:53:25.401] web.cc:447: Couldn't fetch 'https://mirror.worldhotspot.org/archlin … x86_64.iso': expected HTTP response code 206, got 404
Prog[2024-06-10 09:53:25.549] web.cc:447: Couldn't fetch 'https://mirror.worldhotspot.org/archlin … x86_64.iso': expected HTTP response code 206, got 404
Progress: 0.0%, dl from 0 of 0 peers (932 kB/s), ul to 0 (0 kB/s) [0.00]
Stopping torrent...
[2024-06-10 09:53:28.500] archlinux-2024.06.01-x86_64.iso: Pausing torrent
Progress: 0.0%, dl from 0 of 0 peers (973 kB/s), ul to 0 (0 kB/s) [0.00]
```

Lone_Wolf · 2024-06-10 09:48:50

I usually run transmission-daemon using the web interface to control it, so had to tell transmission-cli to use the transmission-daemon folder for config .
(each transmission variant has their own settings, so there can be upto 4 different config folders) .

Other then that, no problem downloading from 50 peers and transmission-cli automatically switched to uploading .

$ transmission-cli --config-dir ~/.config/transmission-daemon/ ~/Downloads/Torrentfiles/archlinux-2024.06.01-x86_64.iso.torrent 
transmission-cli 4.0.6 (38c164933e)
Seeding, uploading to 0 of 50 peer(s), 0 kB/s [0.00]                              
Stopping torrent...
Seeding, uploading to 0 of 50 peer(s), 0 kB/s [0.00]                            
$

Tranmission-cli was updated to 4.06 a week ago, I suggest you run pacman -Syu to update your system then try again .

Arch Linux

#1 2023-06-17 13:21:26

Why are rarely any torrent seeders available for downloading the ISO?

#2 2023-06-17 15:24:33

Re: Why are rarely any torrent seeders available for downloading the ISO?

#3 2023-06-18 09:28:39

Re: Why are rarely any torrent seeders available for downloading the ISO?

#4 2023-06-18 11:28:32

Re: Why are rarely any torrent seeders available for downloading the ISO?

#5 2023-06-18 11:34:34

Re: Why are rarely any torrent seeders available for downloading the ISO?

#6 2023-06-18 11:39:03

Re: Why are rarely any torrent seeders available for downloading the ISO?

#7 2024-06-10 06:53:57

Re: Why are rarely any torrent seeders available for downloading the ISO?

#8 2024-06-10 09:48:50

Re: Why are rarely any torrent seeders available for downloading the ISO?

Board footer