INFO:Download:On - Torrent Metadata

[teddyrogers]

When I was going through the logs I noticed this entry of a torrent file not in my Tribler queue, and not a file I have downloaded before. I make the assumption this is a file being shared via my Tribler, as a proxy?

INFOHASH #1 DELETED seems to be the infohash of the torrent with FILENAME DELETED. Could someone explain INFOHASH #2 DELETED, is this a fake DHT of the same file - FakeDHTSession?

INFO:Download:On metadata received alert: **FILENAME DELETED** metadata successfully received
INFO:Download:On state changed alert: **FILENAME DELETED**: state changed to: checking (r)
INFO:Download:On state changed alert: **FILENAME DELETED**: state changed to: downloading
INFO:Download:On torrent checked alert: **FILENAME DELETED** checked
INFO:tribler.core.libtorrent.download_manager.download_manager:Successfully retrieved metainfo for b'**INFOHASH #1 DELETED**'
INFO:Download:Shutting down...
INFO:TorrentChecker:Got response from FakeDHTSession in 2.171000 seconds: TrackerResponse(url='DHT', torrent_health_list=[HealthInfo(seeders=1, leechers=4, last_check=1752142833, self_checked=True, source=<Source.UNKNOWN: 0>, tracker='')])
INFO:TorrentChecker:1 responses for **INFOHASH #1 DELETED** have been received: [TrackerResponse(url='DHT', torrent_health_list=[HealthInfo(seeders=1, leechers=4, last_check=1752142833, self_checked=True, source=<Source.UNKNOWN: 0>, tracker='')])]
INFO:TorrentChecker:Skip health update, the health in the database is fresher or have more seeders
INFO:TorrentChecker:Check health for the torrent: **INFOHASH #2 DELETED**
INFO:TorrentChecker:Trackers for **INFOHASH #2 DELETED**: set()
INFO:TorrentChecker:DHT session has been created for **INFOHASH #2 DELETED**: FakeDHTSession[DHT, DHT]

[qstokkink]

Tribler passively collects torrents and checks if they're still alive (i.e., whether they have seeders and leechers > 0). This is what you're seeing here and it is used to power Tribler's search and popular torrents features.

[teddyrogers]

Thank you for the response. Would you be able to explain the INFOHASH #2 DELETED, is this a fake DHT of the same file - FakeDHTSession?

[qstokkink]

Your question is mixing a few things. I'll do my best to separate them.

The filename could be the same for infohash 1 and 2. So, I can't say anything about that.

What I can say is that the first 9 lines belong to the final steps of the health check (determining seeders and leechers, like I mentioned before) for infohash 1 and the last three lines are starting another health check for infohash 2. What you posted is truncated logging output for two different health checks.

"FakeDHTSession" is the name of Tribler's implementation to retrieve seeders and leechers for an infohash through the Bittorrent Mainline DHT.