update event from peer that is not in swarm node.js bittorrent tracker error about bittorrent-tracker HOT 3 CLOSED

This error happens when you restart the tracker server. Restarting the tracker will discard all the peers it's tracking. Then, clients that are already running will continue to send update events, but the tracker throws them away because it was expected to get a start event first.

This should only be a warning, and not a fatal error. I just made the following changes:

• unexpected started event (for peer already in swarm) is treated as an update
• unexpected stopped event is discarded
• unexpected completed event is treated as a start
• unexpected update event (from peer not in swarm) is treated as start

Please update to 2.8.0 and let me know if this fixes your issue.

from bittorrent-tracker.

If failse at if (left === 0) peer.complete = true . If i comment this part it started working and some of my old torrents got downloaded with this tracker. However, for newly create torrents it is still not syncing.

It is telling my invalid peer_id for some of them . Do i need to again apply patch for peer_id issue which was having with utorrent and some of the client.

Also, it would be great if you can inform me from where i can retrieve infoHash required for code //server.torrents[infoHash].complete

// get the number of leechers for a particular torrent
//server.torrents[infoHash].incomplete

// get the peers who are in a particular torrent swarm
//server.torrents[infoHash].peers

Thanks

from bittorrent-tracker.

The issue you mentioned should be fixed now if you update to 2.8.2. Feel free to open a new issue if you encounter any new issues.

Not sure why you're seeing invalid peer_id. What bittorrent client are you using to connect to this tracker?

infoHash is just the torrent info hash that identifies the torrent whose info you want to look up. You can get a full list by just doing: server.torrents and that will let you inspect everything.

from bittorrent-tracker.