проблема с KTorrent
Автор
Сообщение
ivann ®
Стаж: 15 лет
Сообщений: 2
Откуда: Уфа
Раньше ktorrent работал нормально. Сейчас максимум один личер подключается и качает. В системе вроде ничего не делал. Еще недавно инет отрубился — сказали в вашем микройоне какое-то оборудование крякнуло; потом восстановили, и после этого заметил указаную проблему, хотя может это и не связано.
$ ktorrent --debug
Bound to port 6881
Loading /home/ivann/.kde3.5/share/apps/ktorrent/tor0/
Encoding : UTF-8
Multi file torrent
OutputPath = /mnt/ivann-ntfs/music-ivann/Lumen/
Starting download
Loading list of peers from /home/ivann/.kde3.5/share/apps/ktorrent/tor0/peer_list (num_peers = 0)
Selected tracker http://torrents.local/bt/announce.php?uk=******& (tier = 1)
Switching to tracker http://torrents.local/bt/announce.php?uk=******&
Doing tracker request to url : http://torrents.local/bt/announce.php?uk=******&&peer_id=-KT2280-8DDKpsTQVO9L&port=6881&uploaded=0&downloaded=0&left=0&compact=1&numwant=100&key=1683545084&event=started&info_hash=x%e8H%8a%60T%d7%05%8c%e0Cg%8a%d2%17%bamy%e1%d2
...
Loading plugin Search
Loading plugin Info Widget
Loading plugin IP Filter
Loading Anti-P2P filter...
AntiP2P header loaded.
IP 0.0.0.0 banned.
Starting minimized
File limit allready at maximum
Data limit allready at maximum
Doing scrape request to url : http://torrents.local/bt/scrape.php?uk=******&&info_hash=%b5v%93%c1%c6S%df%99%10%b4%e5%d6%5b%5eF%f8G%a8%d5%e8
...
Initiating connection to 10.160.154.73
Initiating connection to 10.161.157.119
Initiating connection to 10.163.20.215
Initiating connection to 10.165.150.127
Initiating connection to 172.27.20.59
Initiating connection to 172.27.26.194
Initiating connection to 172.27.27.171
Initiating connection to 172.27.28.231
Initiating connection to 172.27.30.183
Initiating connection to 172.27.30.245
Initiating connection to 77.79.158.232
Initiating connection to 92.50.166.140
Initiating connection to 92.50.174.9
Initiating connection to 92.50.184.81
Initiating connection to 94.41.165.63
Initiating connection to 10.160.130.149
Initiating connection to 10.166.45.48
Initiating connection to 10.167.160.124
Initiating connection to 10.169.155.135
Initiating connection to 172.27.24.148
Initiating connection to 172.27.29.167
Initiating connection to 172.27.45.83
Initiating connection to 77.79.186.48
Initiating connection to 92.50.174.9
Initiating connection to 94.41.175.70
Initiating connection to 94.41.69.105
Initiating connection to 10.167.158.21
Initiating connection to 172.27.13.80
Initiating connection to 172.27.21.25
Initiating connection to 172.27.23.83
Initiating connection to 172.27.29.46
Initiating connection to 172.27.31.203
Initiating connection to 172.27.32.8
Initiating connection to 172.27.9.165
Initiating connection to 92.50.174.9
Initiating connection to 94.41.17.189
Authentication to 10.160.154.73 : ok
Starting socketmonitor threads
Authentication to 10.163.20.215 : ok
Authentication to 10.165.150.127 : ok
Authentication to 172.27.20.59 : ok
Authentication to 172.27.26.194 : ok
Authentication to 172.27.28.231 : ok
Authentication to 172.27.30.183 : ok
Authentication to 172.27.30.245 : ok
Authentication to 92.50.166.140 : ok
Authentication to 92.50.184.81 : ok
Authentication to 10.160.130.149 : ok
Authentication to 10.166.45.48 : ok
Authentication to 10.167.160.124 : ok
Authentication to 172.27.24.148 : ok
Authentication to 172.27.45.83 : ok
Authentication to 94.41.69.105 : ok
Authentication to 10.167.158.21 : ok
Authentication to 172.27.21.25 : ok
Authentication to 172.27.31.203 : ok
Authentication to 172.27.32.8 : ok
Authentication to 172.27.9.165 : ok
Authentication to 94.41.17.189 : ok
Lets not connect to our self
Authentication(S) to 92.50.174.9 : failure
Lets not connect to our self
Authentication(S) to 92.50.174.9 : failure
Lets not connect to our self
Authentication(S) to 92.50.174.9 : failure
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Connection closed
Authentication to 92.50.174.9 : failure
Authentication to 92.50.174.9 : failure
Authentication to 172.27.29.46 : ok
Authentication to 92.50.174.9 : failure
Connection closed
Connection closed
Connection closed
Connection closed
Stopping socketmonitor threads
Authentication to 94.41.175.70 : ok
Starting socketmonitor threads
Connection closed
Stopping socketmonitor threads
Timeout occurred
Authentication to 10.161.157.119 : failure
Timeout occurred
Authentication to 172.27.27.171 : failure
Timeout occurred
Authentication to 77.79.158.232 : failure
Timeout occurred
Authentication to 94.41.165.63 : failure
Timeout occurred
Authentication to 10.169.155.135 : failure
Timeout occurred
Authentication to 172.27.29.167 : failure
Timeout occurred
Authentication to 77.79.186.48 : failure
Timeout occurred
Authentication to 172.27.13.80 : failure
Timeout occurred
Authentication to 172.27.23.83 : failure
Authentication(S) to 172.27.27.128 : ok
Starting socketmonitor threads
Connection closed
Stopping socketmonitor threads
ivann ®
Стаж: 15 лет
Сообщений: 2
Откуда: Уфа
Похоже, что проблема была из-за рейтинга (меньше 0.4). Как-то странно, что трекер не даёт много раздавать если маленький рейтинг (доступно не более одного соединения).
Топик был перенесен из форума Вопросы по BitTorrent сети и ее клиентам в форум Архив
BLACK_M
Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете голосовать в опросах
Вы не можете прикреплять файлы к сообщениям
Вы не можете скачивать файлы
Текущее время: 28-Апр 12:44
Часовой пояс: UTC + 5
| Автор | Сообщение |
|---|---|
|
ivann ®
Стаж: 15 лет |
|
|
Раньше ktorrent работал нормально. Сейчас максимум один личер подключается и качает. В системе вроде ничего не делал. Еще недавно инет отрубился — сказали в вашем микройоне какое-то оборудование крякнуло; потом восстановили, и после этого заметил указаную проблему, хотя может это и не связано.
$ ktorrent --debug Bound to port 6881
Loading /home/ivann/.kde3.5/share/apps/ktorrent/tor0/ Encoding : UTF-8 Multi file torrent OutputPath = /mnt/ivann-ntfs/music-ivann/Lumen/ Starting download Loading list of peers from /home/ivann/.kde3.5/share/apps/ktorrent/tor0/peer_list (num_peers = 0) Selected tracker http://torrents.local/bt/announce.php?uk=******& (tier = 1) Switching to tracker http://torrents.local/bt/announce.php?uk=******& Doing tracker request to url : http://torrents.local/bt/announce.php?uk=******&&peer_id=-KT2280-8DDKpsTQVO9L&port=6881&uploaded=0&downloaded=0&left=0&compact=1&numwant=100&key=1683545084&event=started&info_hash=x%e8H%8a%60T%d7%05%8c%e0Cg%8a%d2%17%bamy%e1%d2 ... Loading plugin Search Loading plugin Info Widget Loading plugin IP Filter Loading Anti-P2P filter... AntiP2P header loaded. IP 0.0.0.0 banned. Starting minimized File limit allready at maximum Data limit allready at maximum Doing scrape request to url : http://torrents.local/bt/scrape.php?uk=******&&info_hash=%b5v%93%c1%c6S%df%99%10%b4%e5%d6%5b%5eF%f8G%a8%d5%e8 ... Initiating connection to 10.160.154.73 Initiating connection to 10.161.157.119 Initiating connection to 10.163.20.215 Initiating connection to 10.165.150.127 Initiating connection to 172.27.20.59 Initiating connection to 172.27.26.194 Initiating connection to 172.27.27.171 Initiating connection to 172.27.28.231 Initiating connection to 172.27.30.183 Initiating connection to 172.27.30.245 Initiating connection to 77.79.158.232 Initiating connection to 92.50.166.140 Initiating connection to 92.50.174.9 Initiating connection to 92.50.184.81 Initiating connection to 94.41.165.63 Initiating connection to 10.160.130.149 Initiating connection to 10.166.45.48 Initiating connection to 10.167.160.124 Initiating connection to 10.169.155.135 Initiating connection to 172.27.24.148 Initiating connection to 172.27.29.167 Initiating connection to 172.27.45.83 Initiating connection to 77.79.186.48 Initiating connection to 92.50.174.9 Initiating connection to 94.41.175.70 Initiating connection to 94.41.69.105 Initiating connection to 10.167.158.21 Initiating connection to 172.27.13.80 Initiating connection to 172.27.21.25 Initiating connection to 172.27.23.83 Initiating connection to 172.27.29.46 Initiating connection to 172.27.31.203 Initiating connection to 172.27.32.8 Initiating connection to 172.27.9.165 Initiating connection to 92.50.174.9 Initiating connection to 94.41.17.189 Authentication to 10.160.154.73 : ok Starting socketmonitor threads Authentication to 10.163.20.215 : ok Authentication to 10.165.150.127 : ok Authentication to 172.27.20.59 : ok Authentication to 172.27.26.194 : ok Authentication to 172.27.28.231 : ok Authentication to 172.27.30.183 : ok Authentication to 172.27.30.245 : ok Authentication to 92.50.166.140 : ok Authentication to 92.50.184.81 : ok Authentication to 10.160.130.149 : ok Authentication to 10.166.45.48 : ok Authentication to 10.167.160.124 : ok Authentication to 172.27.24.148 : ok Authentication to 172.27.45.83 : ok Authentication to 94.41.69.105 : ok Authentication to 10.167.158.21 : ok Authentication to 172.27.21.25 : ok Authentication to 172.27.31.203 : ok Authentication to 172.27.32.8 : ok Authentication to 172.27.9.165 : ok Authentication to 94.41.17.189 : ok Lets not connect to our self Authentication(S) to 92.50.174.9 : failure Lets not connect to our self Authentication(S) to 92.50.174.9 : failure Lets not connect to our self Authentication(S) to 92.50.174.9 : failure Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Connection closed Authentication to 92.50.174.9 : failure Authentication to 92.50.174.9 : failure Authentication to 172.27.29.46 : ok Authentication to 92.50.174.9 : failure Connection closed Connection closed Connection closed Connection closed Stopping socketmonitor threads Authentication to 94.41.175.70 : ok Starting socketmonitor threads Connection closed Stopping socketmonitor threads Timeout occurred Authentication to 10.161.157.119 : failure Timeout occurred Authentication to 172.27.27.171 : failure Timeout occurred Authentication to 77.79.158.232 : failure Timeout occurred Authentication to 94.41.165.63 : failure Timeout occurred Authentication to 10.169.155.135 : failure Timeout occurred Authentication to 172.27.29.167 : failure Timeout occurred Authentication to 77.79.186.48 : failure Timeout occurred Authentication to 172.27.13.80 : failure Timeout occurred Authentication to 172.27.23.83 : failure Authentication(S) to 172.27.27.128 : ok Starting socketmonitor threads Connection closed Stopping socketmonitor threads |
|
|
ivann ®
Стаж: 15 лет |
|
|
Похоже, что проблема была из-за рейтинга (меньше 0.4). Как-то странно, что трекер не даёт много раздавать если маленький рейтинг (доступно не более одного соединения).
|
|
|
Топик был перенесен из форума Вопросы по BitTorrent сети и ее клиентам в форум Архив
BLACK_M |
|
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете голосовать в опросах
Вы не можете прикреплять файлы к сообщениям
Вы не можете скачивать файлы
Текущее время: 28-Апр 12:44
Часовой пояс: UTC + 5