breugel Posted September 18, 2007 Report Share Posted September 18, 2007 Can any one help? Is there a way to stop them?[06:38:29] 87.154.140.161 : [µTorrent 1.7.2 ]: Got Request while choked: 1694:16384->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Request while choked: 4074:2342912->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2260992->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2277376->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2293760->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2310144->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2326528->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2342912->16384[06:38:39] 75.162.150.171 : [µTorrent 1.7.5 ]: Got Request while choked: 4776:573440->16384[06:38:56] 82.23.83.106 : [µTorrent 1.7.3 ]: Got Cancel Unrequested: 3245:16384->16384[06:38:57] 89.48.42.10 : [µTorrent 1.7.5 ]: Got Request while choked: 7454:2850816->16384[06:38:57] 89.48.42.10 : [µTorrent 1.7.5 ]: Got Request while choked: 7454:2867200->16384[06:38:57] 89.48.42.10 : [µTorrent 1.7.5 ]: Got Request while choked: 7454:2850816->16384[06:38:57] 89.48.42.10 : [µTorrent 1.7.5 ]: Got Request while choked: 7454:2867200->16384[06:38:57] 89.48.42.10 : [µTorrent 1.7.5 ]: Got Request while choked: 7454:2883584->16384[06:39:07] 87.154.140.161 : [µTorrent 1.7.2 ]: Got Request while choked: 2934:16384->16384[06:39:08] 84.9.50.95 : [µTorrent 1.7.5 ]: Got Request while choked: 1962:294912->16384[06:39:16] 210.14.101.197 : [bitLord 1.1 ]: Got Request while choked: 8639:458752->16384 Link to comment Share on other sites More sharing options...
DreadWingKnight Posted September 18, 2007 Report Share Posted September 18, 2007 Disable logging of errors will hide those messages.There is no way to stop them outright. Link to comment Share on other sites More sharing options...
breugel Posted September 18, 2007 Author Report Share Posted September 18, 2007 What do they mean? Are they normal? Link to comment Share on other sites More sharing options...
Lord Alderaan Posted September 18, 2007 Report Share Posted September 18, 2007 Nothing wrong on your side afiak Link to comment Share on other sites More sharing options...
funchords Posted September 18, 2007 Report Share Posted September 18, 2007 They're normal. A peer is only allowed to make a request while UNCHOKED. Once UNCHOKED, the peer doesn't know how long they have before they'll be CHOKED. Because of this, sometimes peers will make requests at the same time that your client decides to change their status to CHOKED. This results in errors such as:[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Request while choked: 4074:2342912->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2260992->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2277376->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2293760->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2310144->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2326528->16384[06:38:32] 67.14.215.172 : [bitComet/0.0.9.3]: Got Cancel Unrequested: 4074:2342912->16384The first line is a request that came in too late. The remaining lines are the client cancelling the requests it made while it was UNCHOKED. The message means that the cancel was received, but your client was not holding any matching requests. Those messages are redundant, but harmless, as no more piece data is sent to a client who is CHOKED, anyway. The CANCEL message is actually intended for cancelling requests while UNCHOKED in the final moments of a download (during End Game Mode). Link to comment Share on other sites More sharing options...
breugel Posted September 19, 2007 Author Report Share Posted September 19, 2007 Thanks for the explanation. Link to comment Share on other sites More sharing options...
HoPeFuLLL Posted November 14, 2007 Report Share Posted November 14, 2007 Why am I only seeing these the last few days? (never before)anyone? Link to comment Share on other sites More sharing options...
YoukaiKyuubi Posted December 17, 2007 Report Share Posted December 17, 2007 Same, this thing only started within the past few days. Does anyone know why? I'm using Rogers, if that helps. I know they throttle and stuff too...I'm going to switch soon to a company called Cybersurf. Link to comment Share on other sites More sharing options...
jewelisheaven Posted December 17, 2007 Report Share Posted December 17, 2007 You are showing extra messages in the logger tab.Information like this has been buzzing through the wire sicne time ephemeral (or since Bram devised the protocol)... What settings are you enabling in Logger tab?Peer Traffic will show HAVE / NOHAVEs. Error messages shows those ones. And Verbose.. well verbose shows everything else. Link to comment Share on other sites More sharing options...
YoukaiKyuubi Posted December 22, 2007 Report Share Posted December 22, 2007 I have not changed any settings whatsoever though. I have had uTorrent set up exactly the same way for...a very long time. But these messages suddenly began to appear accompanied by slow speeds. I guess I'll try to download something this week and see if those messages are still there.EDIT: I am now downloading a 5.91 GB file, with absolutely NO LOG MESSAGES. I'm also reaching my max speed, and I've been downloading this torrent for 6 hours now. Furthermore, I was downloading 3 other torrents earlier today, though they were very small, 10 MB each, but still, no error messages. This leads me to believe that my ISP had something to do with the errors before. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.