paranoid Posted September 29, 2008 Report Share Posted September 29, 2008 Some peers gives this error when they connect to the torrent. They will connect initially, speed will rise to around 1MB/s then they disconnect with that error. They`ll continue through out the torrent getting small bursts of data until complete.[2008-09-29 17:13:58] xxx.xxx.xxx.xxx:48690: [µTorrent 1.8 (34.5)]: Disconnect: Peer error: Error 10022(utorrent 1.8 running on a dedi)System is Debian Etch running Wine 1.1.5 (initially 1.1, upgraded attempting to fix the error)I`ve ran Ubuntu Server (hardy) with all available Wine versions, changed ports, flushed iptables but the error still occurs so I`m at a dead end on how to fix it.Has anyone encountered this problem before ? Link to comment Share on other sites More sharing options...
thelittlefire Posted September 30, 2008 Report Share Posted September 30, 2008 Why did you double post, in the OS X thread?Searching for 10022 here brings up similar problems, but not just limited to WINE users. :/ Something is broken, how often does this happen? Link to comment Share on other sites More sharing options...
Switeck Posted September 30, 2008 Report Share Posted September 30, 2008 Probably something like this was what triggered the Peer Error 10022:[2008-09-28 01:17:15] Incoming connection from 90.201.x.x:33301[2008-09-28 01:17:16] 90.201.x.x:33301: [KTorrent/3.1.2.0 (0.0)]: Encrypted handshake completed[2008-09-28 01:17:17] Incoming connection from 90.201.x.x:33306[2008-09-28 01:17:17] 90.201.x.x:33306: Disconnect: Incoming legacy not allowed[2008-09-28 01:17:21] 90.201.x.x:33301: [KTorrent/3.1.2.0 (0.0)]: Disconnect: Peer error: Error 10022I informed alus about it.The latest v1.8.1 beta supposedly fixes it.http://forum.utorrent.com/viewtopic.php?pid=363336#p363336 Link to comment Share on other sites More sharing options...
paranoid Posted September 30, 2008 Author Report Share Posted September 30, 2008 Doesnt seem to indicate anything to do with legacy not allowed since I`m running with encryption enabled allowing incoming legacy connections. [2008-09-30 10:41:50] 202.27.xxx.xxx:27613: Connecting: source: TI[2008-09-30 10:41:52] 202.27.xxx.xxx:27613: [µTorrent/1.7.7.0 (0.0)]: Encrypted handshake completed[2008-09-30 10:41:59] 202.27.xxx.xxx:27613: [µTorrent 1.7.7 (5.5)]: Disconnect: Peer error: Error 10022So I tried with encryption disabled and the error`s still occur.[2008-09-30 10:52:18] 85.204.xxx.xxx:49629: Connecting: source: T[2008-09-30 10:52:18] 85.204.xxx.xxx:49629: [µTorrent/1.8.0.0 (0.0)]: Handshake completed[2008-09-30 10:52:23] 85.204.xxx.xxx:49629: [µTorrent 1.8 (73.3)]: Disconnect: Peer error: Error 10022As you can see theres not much indication on why it is happening, apart from viewing the peer bursting to just over 1MB/s then it drops. The peers above show their client as uTorrent but I`ve seen other clients give the same error.I tried the beta yesterday and the problem still persists and I`ve tried also reseting utorrent settings to default.Anyway I see that there is a bug report on this issue at WineHQ which was open 2008-06-29. Running utorrent 1.7.7 on Wine 1.0.0 (but 0.9.55 is the same) on ubuntu 7.04feisty (Intel based).When seeding and single peer reaches speed above approx 1MB/s it disconnectsthis peer with the following error: Peer error: Error 10022. Seeding to peers with speed below 1MB/s works well and is not affected by thisdisconnections.Consulted with utorrent developers and they are not aware of this behavior onany other platform.http://bugs.winehq.org/show_bug.cgi?id=14188Why did you double post, in the OS X thread?Thought it was relevant post in there since it`s for linux users too not just mac. Perhaps some of them have seen this error before. Link to comment Share on other sites More sharing options...
Switeck Posted September 30, 2008 Report Share Posted September 30, 2008 The problem has nothing to do with connections being encryption or legacy.The problem is uTorrent wasn't checking for existing duplicate incoming connections before allowing an incoming connection from an ip.(In v1.8 uTorrent may even have this condition with both incoming and outgoing connections!)The 2nd incoming connection should be dropped automatically...it isn't, and that somehow triggers the 10022 error.The latest v1.8.1 beta supposedly fixes this. Link to comment Share on other sites More sharing options...
paranoid Posted September 30, 2008 Author Report Share Posted September 30, 2008 I`ve tried build 12495 and as soon as I jumped on a torrent which had fast peers I got error 10022 popping up. This is using ubuntu hardy with wine 1.1.5[2008-09-30 18:20:56] 88.191.90.xxx:49363: [µTorrent 1.7.7 (32.6)]: Disconnect: Peer error: Error 10022[2008-09-30 18:20:57] 76.2.159.xx:49155: Disconnect: Connection closed[2008-09-30 18:20:58] 76.2.159.xx:49155: Disconnect: Connection closed[2008-09-30 18:20:58] 85.196.112.xxx:42471: [µTorrent 1.8 (33.0)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:01] 81.217.122.xx:39312: [µTorrent 1.8 (18.7)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:01] [<ERROR>]:xxx: Disconnect: Peer error: Error 10047[2008-09-30 18:21:03] 91.121.80.xxx:51241: [µTorrent 1.7.7 (35.8)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:04] 213.186.57.xxx:63669: [µTorrent 1.8 (36.0)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:04] 91.121.141.xx:44407: [µTorrent 1.8 (36.2)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:07] 66.32.66.xxx:26937: Disconnect: Peer error: Error 10061[2008-09-30 18:21:07] 213.114.73.xxx:59240: [µTorrent 1.8 (36.6)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:12] 91.121.108.xx:48044: [µTorrent 1.8 (40.0)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:12] [<ERROR>]:13971: Disconnect: Peer error: Error 10047[2008-09-30 18:21:14] 91.121.105.xx:35994: [µTorrent 1.8 (35.0)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:14] [<ERROR>]:52812: Disconnect: Peer error: Error 10047[2008-09-30 18:21:15] 85.17.109.xx:40744: [libTorrent 0.11.9 (36.6)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:17] 81.156.81.xxx:18099: Disconnect: Timed out[2008-09-30 18:21:23] 80.244.76.xxx:64484: [µTorrent 1.8 (1.3)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:23] 71.139.156.xxx:52151: Disconnect: Connection closed[2008-09-30 18:21:25] [<ERROR>]:60141: Disconnect: Peer error: Error 10047[2008-09-30 18:21:27] 62.212.74.xxx:38598: [µTorrent 1.8 (0.5)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:33] 88.191.90.xxx:59538: [µTorrent 1.7.7 (51.9)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:36] [<ERROR>]:39312: Disconnect: Peer error: Error 10047[2008-09-30 18:21:38] 91.121.80.xxx:2507: [µTorrent 1.7.7 (54.8)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:39] 91.121.116.xx:1588: [µTorrent 1.8.1 (0.0)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:39] [<ERROR>]:19643: Disconnect: Peer error: Error 10047[2008-09-30 18:21:39] [<ERROR>]:28800: Disconnect: Peer error: Error 10047[2008-09-30 18:21:42] 91.121.141.xx:46621: [µTorrent 1.8 (56.1)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:48] 91.121.105.xx:4852: [µTorrent 1.8 (56.1)]: Disconnect: Peer error: Error 10022[2008-09-30 18:21:52] [<ERROR>]:42471: Disconnect: Peer error: Error 10047[2008-09-30 18:21:57] [<ERROR>]:38431: Disconnect: Peer error: Error 10047[2008-09-30 18:22:02] 62.212.74.xxx:48211: [µTorrent 1.8 (60.8)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:04] 213.186.57.xxx:63669: Disconnect: Connection closed[2008-09-30 18:22:05] 80.244.76.xxx:46772: [µTorrent 1.8 (39.8)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:05] 81.217.122.xx:32312: [µTorrent 1.8 (40.2)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:15] 91.121.108.xx:48044: Disconnect: Connection closed[2008-09-30 18:22:16] 91.121.116.xx:32459: [µTorrent 1.8.1 (0.0)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:20] 213.114.73.xxx:59240: [µTorrent 1.8 (81.7)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:21] [<ERROR>]:52812: Disconnect: Peer error: Error 10047[2008-09-30 18:22:22] 91.121.80.xxx:2521: [µTorrent 1.7.7 (85.9)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:23] 66.32.66.xxx:26937: Disconnect: Peer error: Error 10061[2008-09-30 18:22:26] 91.121.105.xx:4859: [µTorrent 1.8 (83.4)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:33] 83.250.42.xxx:57715: Disconnect: No such torrent: B10378CEBC474AA87DA3FA549C2FBC32CD7E20A3[2008-09-30 18:22:37] 213.208.116.xxx:12000: Disconnect: Connection closed[2008-09-30 18:22:37] 91.121.178.xxx:50086: [libTorrent 0.11.9 (77.4)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:37] 85.196.112.xxx:42471: [µTorrent 1.8 (97.9)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:38] 91.121.141.xx:44407: [µTorrent 1.8 (97.1)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:39] 88.191.90.xxx:59669: [µTorrent 1.7.7 (97.0)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:39] 213.208.116.xxx:12000: Disconnect: Connection closed[2008-09-30 18:22:41] [<ERROR>]:13971: Disconnect: Peer error: Error 10047[2008-09-30 18:22:48] 216.180.224.xxx:49205: Disconnect: Connection closed[2008-09-30 18:22:48] 206.248.181.xx:52812: Disconnect: Peer error: offline (timed out)[2008-09-30 18:22:48] 80.244.76.xxx:64686: [µTorrent 1.8 (89.5)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:49] 62.212.74.xxx:48211: Disconnect: Connection closed[2008-09-30 18:22:49] 216.180.224.xxx:49205: [BitTornado/03H (0.0)]: Disconnect: Connection closed[2008-09-30 18:22:49] 58.8.73.xxx:55653: Disconnect: Peer error: offline (timed out)[2008-09-30 18:22:51] 83.241.45.xxx:3795: [µTorrent 1.8 (0.8)]: Disconnect: Peer error: Error 10022[2008-09-30 18:22:51] 77.96.134.xx:32498: Disconnect: Peer error: offline (timed out)For now I`ve changed over to using rtorrent/wtorrent until I can solve the problem. Link to comment Share on other sites More sharing options...
thelittlefire Posted September 30, 2008 Report Share Posted September 30, 2008 More information is useful. Like not just logging disconnect errors for one. Hmm.ERROR before port means your OS can't understand IPv6 addresses. . . Link to comment Share on other sites More sharing options...
Firon Posted September 30, 2008 Report Share Posted September 30, 2008 There's two Wine bugs here. One, wine is formatting IPv6 addresses incorrectly. Two, it's dropping peers when it shouldn't be. Link to comment Share on other sites More sharing options...
paranoid Posted September 30, 2008 Author Report Share Posted September 30, 2008 ERROR before port has only surfaced since using the latest beta, it never happened on 1.8 stable. WHat other information would be helpful ? Link to comment Share on other sites More sharing options...
thelittlefire Posted September 30, 2008 Report Share Posted September 30, 2008 So 11813 detects IPv6 OK? ... You sure, it's [xxxx:xxxx:xxxx:xxxx:xxxx:xxxx] formatted, and they show up fine?As far as troubleshooting 10022 is it possible your firewall is broken? Link to comment Share on other sites More sharing options...
Firon Posted September 30, 2008 Report Share Posted September 30, 2008 The IPv6 formatting issue is a Wine bug, since it works on actual Windows. Ditto for disconnecting at 1MB/s.(alus) looks like WSAStringToAddressA works, but WSAAddressToStringA does not Link to comment Share on other sites More sharing options...
thelittlefire Posted September 30, 2008 Report Share Posted September 30, 2008 [ERROR] post http://forum.utorrent.com/viewtopic.php?pid=363137#p363137But nothing about 10022 that I could find. Link to comment Share on other sites More sharing options...
paranoid Posted October 1, 2008 Author Report Share Posted October 1, 2008 On firewall I`m just using iptables with firestarter front end. I`ve flushed the tables but it doesnt help.For stuff on 10022 there is a few threads in forums on the issue. The one below is the only public thread and the rest are on private sites.http://filesharingtalk.com/vb3/f-seedbox-discussion-154/t-utorrentwine-issues-ubuntu-314188/?How to to solve it seems sketchy with some saying they had to downgrade wine or change OS to debian/ubuntu 7.04 but they cant be confirmed since the problems seem to persists for others doing the same. It does seem to be a problem with seedbox`s on mainly OVH boxes but theres reports of other providers too. Link to comment Share on other sites More sharing options...
solidburn Posted October 4, 2008 Report Share Posted October 4, 2008 Hi im use Ubuntu 8.04 and im have the same problem v1.8.1 doesn't resolved but im install wine ver wine_0.9.33~winehq0~ubuntu~6.10-2_i386.deb and this fix the problem but the wine is so old Link to comment Share on other sites More sharing options...
paranoid Posted October 4, 2008 Author Report Share Posted October 4, 2008 I`ve not been able to test that previous back since I`m using x64 system but I`m just about to test it on a temp box. So far looks like wine is defiantly the problem here.Edit: temp box is running fine using that version. It`s just down to finding out whats changed from this version and the current one.Edit: There`s been a fix applied to the latest version of wine to fix this error. Use Git to obtain the latest source. http://www.winehq.org/site/git Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.