whirledps Posted December 23, 2007 Report Posted December 23, 2007 My seeding to clients is stopping at 99.7% no matter how long it runs. It says it continues to up load and it certainly should have completed these clients by now.I have no hash errors, the debug - which I don't understand is giving me high numbers on the left | and -1 on the right.I have not had this problem in seeding before or downloading - even at high speeds. Help is appreciated!!!P.S. Why am I getting download kbs from different clients on a torrent I am seeding and is complete?? Is someone screwing up my torrent?Here is a snip of the log:[12:53:14] Incoming connection from 68.144.30.116[12:53:16] 68.144.30.116 : Disconnect: Can't sync DH3[12:53:20] Incoming connection from 85.149.156.54[12:53:20] 85.149.156.54 : Disconnect: Too many local connections[12:53:25] Incoming connection from 70.238.190.47[12:53:26] Incoming connection from 90.34.112.62[12:53:26] 84.104.55.103 : [bitLord 1.1 ]: Disconnect: Connection closed[12:53:26] 90.34.112.62 : [Ares/2.0.9.3 ]: Handshake completed[12:53:27] 70.238.190.47 : Disconnect: Too many local connections[12:53:27] Incoming connection from 82.38.13.182[12:53:27] 82.38.13.182 : Disconnect: Too many local connections[12:53:27] Incoming connection from 85.237.17.180[12:53:30] 85.237.17.180 : Disconnect: Too many local connections[12:53:37] Incoming connection from 82.224.239.120[12:53:37] 82.224.239.120 : Disconnect: Connection closed[12:53:39] Incoming connection from 82.38.13.182[12:53:39] 82.38.13.182 : Disconnect: Too many local connections[12:53:45] Incoming connection from 24.91.113.212[12:53:45] 24.91.113.212 : Disconnect: Connection closed[12:53:50] Incoming connection from 24.65.132.110[12:53:50] 24.65.132.110 : Disconnect: Can't sync DH3[12:53:58] Incoming connection from 71.211.155.123[12:53:58] 71.211.155.123 : Disconnect: Too many local connections[12:53:58] Incoming connection from 83.114.68.117[12:53:59] 83.114.68.117 : Disconnect: Can't sync DH3
DreadWingKnight Posted December 23, 2007 Report Posted December 23, 2007 Stop the torrent, right-click, force a re-check.Does the file maintain its 100% complete state?
whirledps Posted December 23, 2007 Author Report Posted December 23, 2007 Thanks. I just did that. No, it does not retain 100% it now reads 99.7% which explains my clients stopping at 99.7%.Do I need to recreate the torrent? I know the video is complete, I have watched it before.I searched the FAQ and the forums, but did not locate a situation that matched mine. If I missed it, please forgive me. I only want to finish seeding a dead torrent for others to enjoy.Thanks for your help.
DreadWingKnight Posted December 23, 2007 Report Posted December 23, 2007 The problem is likely that a media application on your system re-tagged the video without your knowledge or consent.You will need to disable that function THEN re-make the torrent in order to be able to seed it again.
whirledps Posted December 23, 2007 Author Report Posted December 23, 2007 Very possible! I installed a video player yesterday afternoon. I have removed all file associations with it. I have created a new torrent overwriting the original. Do I need to post the new torrent to a web site even through it has the same name? Not sure if it may have a unique ID associated with it or something... Or just let that torrent begin seeding and it will take up where the last left off....What's odd is that I had another torrent complete seeding with the same extension without problems.I am new to the torrent world, always used emule until recently. Sorry if I am asking dumb questions.Thanks!~whirledps
DreadWingKnight Posted December 23, 2007 Report Posted December 23, 2007 Yes you do, there is an infohash that defines what the torrent is.New peers won't see you if you don't upload the new torrent.
whirledps Posted December 23, 2007 Author Report Posted December 23, 2007 Gotcha! That's what I was thinking, the hash to identify the file. Thank you very much for your assistance.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.