You are not logged in.
on my seed box I have Helium and Deuterium, but they keep throwing errors. I have been seeding these ones for while, without problems, but for the last 2ish days they are having problems talking with the tracker. I haven't changed any firewall settings, my other distros are seeding just fine, they both have been verified, and when I re-announce them they work just fine, well for a little while. Transmission doesn't really give me any information, other than:
Tracker gave an error: Connection failed
Is there something going on with the tracker, because I am almost positive that it isn't a problem on my end? I have even verified that the tracker's address is correct, the only thing I haven't done is delete the whole torrent (data and all), and re-download it.
I really enjoy being able to give back by seeding, so I would like to get this resolved as soon as I can.
Last edited by ansem_of_nexus (2018-06-17 18:30:35)
Offline
@nobody is the man for this question, but have you tried deleting the torrent files (NOT the ISO files themeselves) and then downloading the torrents again from bunsenlabs.org?
I don't care what you do at home. Would you care to explain?
Offline
I've only been seeding sporadically, but I just saw this after seeding for an hour...
Please Verify Local Data! Piece #3875 is corrupt.
That was the 64 bit ISO. The minimal one stalled, 32 bit had no uploaders.
I don't care what you do at home. Would you care to explain?
Offline
on my seed box I have Helium and Deuterium, but they keep throwing errors. I have been seeding these ones for while, without problems, but for the last 2ish days they are having problems talking with the tracker. I haven't changed any firewall settings, my other distros are seeding just fine, they both have been verified, and when I re-announce them they work just fine, well for a little while. Transmission doesn't really give me any information, other than:
Tracker gave an error: Connection failed
Is there something going on with the tracker, because I am almost positive that it isn't a problem on my end? I have even verified that the tracker's address is correct, the only thing I haven't done is delete the whole torrent (data and all), and re-download it.
I really enjoy being able to give back by seeding, so I would like to get this resolved as soon as I can.
Which torrent file exactly? Please link it.
Which version of Transmission exactly?
The IPv4 or IPv6 tracker?
Can you please seed the file temporarily with rtorrent put the torrent file into the same directory as the ISO, then just "rtorrent $torrentfile" and check if rtorrent starts complaining also?
Offline
I've only been seeding sporadically, but I just saw this after seeding for an hour...
Please Verify Local Data! Piece #3875 is corrupt.
That was the 64 bit ISO. The minimal one stalled, 32 bit had no uploaders.
That's a local error. Is your hard disk OK?
The IPv6 tracker is seriously starving for seeders, there are 3 for amd64 but probably none for the other images. I thought about shutting it down.
You should use a torrent that can read from webseeds, like qBittorrent, it'll download the image from the server instead. All our images are seedable from webseeds this way. rtorrent does not support webseeds.
Oh, and qbittorrent says "stalled" when it is "idle", that's not an error.
Offline
ok, first up, the information:
transmission
VERSION
Daemon version: 2.92 (14714)
RPC version: 15
I rechecked, and I have haven't blocked ipv6, so I should be able to make that work.
as for the torrent info, I got all of them off BL Installation section, I will include the magnet link as the original .torrents were deleted. though I know transmission keeps a copy somewhere, that I could probably dig up. But back to the torrents, I believe they are ipv4:
bl-Deuterium-amd64_20170429.iso
udp://tracker.bunsenlabs.org:6969
magnet:?xt=urn:btih:7105a3932e1126dc60e8c4c81b3fd9928841e4c5&dn=bl-Deuterium-amd64%5F20170429.iso&tr=udp%3A%2F%2Ftracker.bunsenlabs.org%3A6969&ws=http%3A%2F%2Fkelaino.bunsenlabs.org%2Fddl%2F
bl-Helium_amd64+build2.iso
udp://tracker.bunsenlabs.org:6969
magnet:?xt=urn:btih:492ecd62162f4972fe8e078c771c37bcd40d507c&dn=bl-Helium%5Famd64%2Bbuild2.iso&tr=udp%3A%2F%2Ftracker.bunsenlabs.org%3A6969&ws=http%3A%2F%2Fkelaino.bunsenlabs.org%2Fddl%2F
I am currently working on trying out rtorrent and will report back with how that works out.
also how do you get the torrents to ipv6, I would gladly seed for both ipv4 and ipv6.
Offline
That's a local error. Is your hard disk OK?
I guess I didn't have the torrent file fully downloaded, it's working fine now.
I'm also using transmission (default torrent client in BL). You're right, 64 bit is seeding fine to 4 peers, CD ISO shows 1 connected peer occasionally but doesn't seed, 32 bit full ISO has 0 peers.
I don't care what you do at home. Would you care to explain?
Offline
I was able to get rtorrent working just fine, but transmission is reporting everything is fine right now too... I don't know, I don't understand why I would be getting errors for almost 2 days straight, just to have it go away.
as for the ipv6, everything I am reading says that since I don't have ipv6 blocked, that transmission should be more than happy to seed for it.
Update:
never mind, still having the same problem, but I didn't have rtorrent running, so have to wait until it happens again.
Update2:
I can't seem to get transmission to connect to the tracker, but it would seem that rtorrent isn't having that problem.
Peer list 0: udp://tracker.bunsenlabs.org:6969
Id: Counters: 0f / 8s (0) on S/L/D: 90/2/0 (0/82)
update3:
Have deleted the torrent from transmission and re-added it, pointed to file and passed verification, but still can't connect to tracker.
Just restarted transmission-daemon and that seems to have let it connect for now, next announcement is in 24 minutes, so I will wait and see if it fails or not.
update4:
seems to be running fine now, announcements aren't having connection errors. So I guess you just need to restart and re-add torrents until they work normally? I will continue watching it and as long as it doesn't throw another error before the end of tomorrow, I guess I will mark this as resolved.
Last edited by ansem_of_nexus (2018-06-14 23:28:42)
Offline
I am currently working on trying out rtorrent and will report back with how that works out.
also how do you get the torrents to ipv6, I would gladly seed for both ipv4 and ipv6.
It's simple, you need to connect to the IPv6 address of tracker.bunsenlabs.org, from an IPv6 address (so if you have a public IPv6 address, just seed the torrent as usual). That tracker only tracks IPv6 addresses, so you'd automatically seed to IPv6 users (only). I don't know of any torrent client which supports resolving 2 different IP addresses (IPv4 and IPv6) for the same tracker and seeding to both. It would need to bind to two different sockets (ipv4 and ipv6). E.g. in rtorrent, one can configure the `bind` config option and launch two rtorrent instances, binding to a different address family socket each.
Offline
I'm seeding 1 peer for the 32 bit full ISO, so everything looks OK here.
I don't care what you do at home. Would you care to explain?
Offline