-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XD seeding anounce problems #62
Comments
try latest commit, if you need a build I can make one. |
Much better now, even speed seems to have improved. Something I came across when testing this: is there a way to know the identity of XD? I mean the four letter identifier, not router session. |
Another issue I'm not sure it's a problem: the number of peers reported by i2psnark is much higher than reported by XD. In i2psnark they seem inactive, so this can be only outdated statistics from tracker or a problem in i2psnark ¿? |
i suspect that i2psnark is tracking peers that are at a very high latency, i2pd has a much stricter latency tolerance on streaming if i recall. |
Actually I think when restarting XD or i2pd my seedbox was still visible (but not seeding) in i2psnark so I had a "ghost" peer and the real one. That was the reason I wanted to know the identity of XD, to distinguish them. |
This still seems problematic. One of the torrents (last added and last in list) seeds fine, but the others didn't have any seeder at 100% on tracker' list (this is the only way I have to know XD assigned identity and if it's seeding correctly). On the other side, webui shows some peers on some torrents and tracker shows clients trying to download. Although this can be some kind of queueing problem. |
if you have |
No, I set it to 0 after your comment. |
Alright I look into it this weekend
…On Tue, Jun 12, 2018 at 04:47:12AM -0700, pkreuzt wrote:
No, I set it to 0 after your comment.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#62 (comment)
|
With latest version 10d1200 Postman still doesn't acknowledge XD as a seeder and shows completedness at 0% |
Can confirm. Even today, I uploaded ~30 torrents, all of them are shown as seeding in XD but on Postman there are no seeders. My client is being identified as a leecher/downloader. |
Problem still exist. Postman shows XD as a leecher for torrents created by me. And shows 0% of progress. |
i'll have to ask postman what the problem could be then. |
I was going to post a new issue about an error message I noticed and how I think it relates to postman never showing my XD seeder, only my snark seeder, but I think it might be this problem. Hopefully this helps: [WRN] 2020-09-03 00:23:32.280907662 -0400 EDT m=+57.421996136 http://tracker2.postman.i2p:80/announce.php got error while announcing: DB error: Out of range value for column 'to_go' at row 1Original Query: INSERT INTO peers ( I'm pretty sure 'to_go' should be 0 for a seeding torrent, not some odd number in scientific notation. ;) I dropped the files into the download directory and pasted the .torrent I created in i2psnark into the web UI. It seeds successfully, it just doesn't show up in the peer list on postman. I don't think any torrent I've seeded with XD ever has, in fact, though I can't say I've ever paid too much attention to the warnings on the XD console so I'm just assuming the same error has been happening all along. If there's any more information I can contribute or if knowing which torrent it is would be helpful I would be glad to provide more information here or, if you need identifying details, privately. Thanks for XD, btw, it's pretty awesome! |
info
git revision / version: 0.2.2
OS: linux
Architecture: armv7
Not sure if important: running through I2PD
problem
XD doesn't anounce itself to tracker when seeding. When being myself the uploader of a torrent, the tracker doesn't get notified about the seeding XD and the seeder count remains zero. The strange thing is it really seeds parts of downloaded torrents. I'm not sure about it, but think it does upload when there is at least another seeder of the file. (If you ask who haves the same file I'm trying to upload, it's my other computer which I sometimes run with Java I2P router and i2psnark).
I see no errors in the log, only some warnings of this kind:
[WRN] 2018-06-09 01:53:08.883803984 +0200 CEST m=+120.590429659 failed to resolve peer NAMING REPLY RESULT=INVALID_KEY NAME=blahblahblahblahblahblahblahblahblahblahblahblahblah.b32.i2p
The text was updated successfully, but these errors were encountered: