[Bug 26031] New: µTorrent (uTorrent) fails listening to a port after a number of persistent connections are opened against it
wine-bugs at winehq.org
wine-bugs at winehq.org
Tue Feb 8 16:06:17 CST 2011
http://bugs.winehq.org/show_bug.cgi?id=26031
Summary: µTorrent (uTorrent) fails listening to a port after a
number of persistent connections are opened against it
Product: Wine
Version: 1.3.13
Platform: All
URL: http://www.utorrent.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
AssignedTo: wine-bugs at winehq.org
ReportedBy: t.artem at mailcity.com
Steps to reproduce:
1) Run µTorrent
2) Incoming connections icon should turn green (port listen: OK), netstat -ln
confirms that
3) Start downloading any torrent
4) Incoming connections icon will turn red (Listen error: you should change the
listen port)
observe these errors logged in uTorrent Logger Tab:
[2011-02-09 02:28:50] *** Starting Diagnostic thread ***
[2011-02-09 02:28:50] IPv6 is installed
[2011-02-09 02:31:46] TCP port bind failed 0.0.0.0:9001: (10048) Error 10048
[2011-02-09 02:32:12] TCP port bind failed 0.0.0.0:9001: (10048) Error 10048
at this point neither Wine, nor µTorrent will be listening to the designated
port:
# netstat -ln -eep | grep 8008
udp 0 0 0.0.0.0:8008 0.0.0.0:*
500 117033 10470/uTorrent.exe
so while uTorrent is listening to the incoming UDP connections, TCP traffic is
unmanaged causing the errors in the µTorrent's Logger Tab.
The strangest thing is that no other application will be able to use this port
(8008):
# nc -vl 8008
nc: Address already in use
However if I order nc to bind to the loopback interface specifically, it will
run:
# nc -vl localhost 8008
[running]
It's worth noting that when wine/uTorrent "listen" abilities break, there are
already some established connections to my_external_IP_address:8008 (right now
I see three such ESTABLISHED connections).
So, probably there's some sort of bug in wine server - it shouldn't stop
listening to a port when persistent connections are made to it - but I'm
totally uncertain about it because I have no idea how wine server (should)
handles TCP traffic.
I can help solving this bug by attaching any required debug information if it's
necessary.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the wine-bugs
mailing list