Skip to content
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

Transfer "dies" for no reason #372

Closed
Stiveknx opened this issue Jul 15, 2015 · 11 comments
Closed

Transfer "dies" for no reason #372

Stiveknx opened this issue Jul 15, 2015 · 11 comments

Comments

@Stiveknx
Copy link
Contributor

@Stiveknx Stiveknx commented Jul 15, 2015

I shared a file on instant.io, then tried to transfer in my client using webtorrent-hybrid in nodejs.

I was the only one sharing the file and, my client was the only one downloading it.
For some reason, the upload "stopped" after 2 mb transfered, and the transfer didn't "move on" anymore.
I reloaded the page in instant.io, selected the file again and the transfer ran for more 15mb and stopped again. The connection simply got "Lost", I'm now trying to find why this is happening.

I tried to enable debug to check where the problem is, but I didn't locate..

How can I try to dectect where the problem is?

PS.: If there's more than 1 seeder, this doesn't happen, only when there's one seeder.

(sorry, bad English)

@Stiveknx Stiveknx changed the title Detect download transfer complete Transfer "dies" for no reason Jul 15, 2015
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 15, 2015

That's weird. No idea why that would be happening. If you get any more info about how to reliably reproduce this, please share!

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 15, 2015

If you can, run webtorrent-hybrid with the environment set to DEBUG=*,-bittorrent-dht and run it until the disconnect happens, then post the log here.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 16, 2015

@Stiveknx Was the seeder in node or in the browser?

If the seeder was in node, I think this may be caused by #375. Please let me know so we can get to the bottom of this.

@Stiveknx

This comment has been minimized.

Copy link
Contributor Author

@Stiveknx Stiveknx commented Jul 16, 2015

Seeder was runing in browser (directly from instant.io).

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 29, 2015

@Stiveknx Can you try this out again on https://instant.io?

If you have a flaky connection to the internet, the webrtc conncections to peers can be lost and would need to be re-established. I just pushed an improvement to the tracker module, so we now try to look for new peers every 30 seconds on the already-established WebSocket connection to the tracker.

This should make things better. Please test it out and let me know if things are better.

@Stiveknx

This comment has been minimized.

Copy link
Contributor Author

@Stiveknx Stiveknx commented Jul 29, 2015

Hi.

So, I did a quick test and apparently the problem has been solved.
I shared the same file I did before and the file started and downloaded without stop.

I'll mark it as closed, but later I'll try to test with more and larger files!

Ps.: Thanks for the amazing project

@Stiveknx Stiveknx closed this Jul 29, 2015
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 30, 2015

Awesome!

@Stiveknx

This comment has been minimized.

Copy link
Contributor Author

@Stiveknx Stiveknx commented Aug 11, 2015

Opening it again ..

sometimes, when I'm almosting finishing the download, it stops when 20 pieces or more are pending ...

Check the debug:
http://pastebin.com/raw.php?i=jcTNZb5D

I've notice that, after "webtorrent:torrent error getting piece", if I have too much of these errors, I got stuck in last pieces.
When the transfer finishes successfully, I don't see much of there messages ...

Edit:
Again, stucked.
http://pastebin.com/raw.php?i=tByn8ra9

@Stiveknx Stiveknx reopened this Aug 11, 2015
@Stiveknx

This comment has been minimized.

Copy link
Contributor Author

@Stiveknx Stiveknx commented Aug 17, 2015

Here's another debug:
http://pastebin.com/raw.php?i=Q6s515Rf

This time, I was seding from my computer to another one ...
I was the only seeder.

Command:

./node_modules/webtorrent-hybrid/bin/cmd.js download 'magnet:?xt=urn:btih:cafef3c80da06542858f68b7a593d0e036345bd7&dn=NVIDIA-Linux-x86_64-340.76.run&tr=wss%3A%2F%2Ftracker.webtorrent.io' &

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jan 3, 2016

This issue is super old. I'm going to close and assume that it's fixed now. If this is not the case, feel free to open a new issue.

@feross feross closed this Jan 3, 2016
@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 5, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.