Node not used for transfers or as exit node


Ubuntu 19.10 here, all last RC, current one 7.5.0-rc5, have the same behaviour:

discovering, searching, downloading and uploading torrents work fine. But, the node is not used as a transfer node or as a exit node.( just 11.5G in weeks). Tested on diferent networks, without restrictions, gibabit connections.

With older versions, even in a complicated network enviroment, it did not alwasy work, bun when it did, i cold expect 30-50G/day.

Any hints, ideas…?


update: all of a sudden it now works normally. After weeks of nothing, after yet another tribler restart, it worked as if nothing was wrong, the tunnel exit sokets was populated, and speed of 3MB in a minute … So i’m guessing there is a module within tribler that usualy dies at startup on my system …


It would be nice if you provide us with relevant Tribler logs from the period when you experienced problems.


dont have those logs…, today got this log, and no real upload done in that time frame (but this time it might have been a network issue)

INFO - TriblerTunnelCommunity(294) - Doing hidden seeders lookup for info_hash b’94deb61e93a3b8d7b87bbbaed47fec3e88bfe12f’
[PID:11732] 2020-05-13 07:40:34,069 - ERROR taskmanager:127 TunnelExitSocket.done_cb(): Task resulted in error: [Errno -2] Name or service not known
[PID:11732] 2020-05-13 07:40:34,080 - ERROR tunnel:146 TunnelExitSocket.on_ip_address(): Can’t resolve ip address for Failure: [Errno -2] Name or service not known

cisf-tribler-PLvF4LIl.log (2.3 MB)


cisf-tribler-zknEpujY.log (2.5 MB)

small log…again no transfers…in the end forced tribler shutdown

Is there documentation on how the system makes decisions to transfer data or not? Is there an external central element influencing this? (it more and more seems so…oO)


We had some troubles with our infrastructure recently, namely exit/bootstrap nodes.