Community Forums Today's Posts     Member List     Archive    
Results 1 to 2 of 2
  1. #1
    Join Date
    Jan 2010
    Location
    Phoenix, AZ
    Posts
    85

    too many tcp close_wait connections with client tsdns bug possibly

    I only noticed this issue with the final release client: 3.0.0 [Build: 14954] on Windows

    I found this problem while trying to connect to some websites with my browser.
    The browser started retrieving nothing and saying done. While investigating I ran tcpview and noticed lots of tcp connections to the same teamspeak server all in a CLOSE_WAIT state.

    Here is what I know has happened. I connect to two virtual servers at the same IP address the first time it happened it was to a server running rc1 on windows, the second time to the final server release 3.0.0 [Build: 14957] on Linux. The problem seems to be with the tsdns server.

    while connected the server was shut down and my client kept trying to connect like it normally does, but I think this is where the CLOSE_WAIT problem occurred, the first time I restarted teamspeak and they all went away, the second time it happened I just closed the connection to both virtual servers, yet all the CLOSE_WAIT connections still remain. It has been hours and they still remain.

    Here is a sample of the tcpview output IP was changed to 10.0.0.154 to protect the server
    Code:
    ts3client_win32.exe:2544	TCP	127.0.0.1:25639	0.0.0.0:0	LISTENING	
    ts3client_win32.exe:2544	UDP	0.0.0.0:1027	*:*		
    ts3client_win32.exe:2544	UDP	0.0.0.0:1030	*:*		
    ts3client_win32.exe:2544	UDP	0.0.0.0:1034	*:*		
    ts3client_win32.exe:2544	UDP	0.0.0.0:1041	*:*		
    ts3client_win32.exe:2544	TCP	192.168.1.3:1055	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	UDP	0.0.0.0:1054	*:*		
    ts3client_win32.exe:2544	UDP	0.0.0.0:1335	*:*		
    ts3client_win32.exe:2544	TCP	192.168.1.3:1626	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:1631	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:1640	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:1649	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:1654	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:1658	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:1662	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	UDP	0.0.0.0:1769	*:*		
    ts3client_win32.exe:2544	TCP	192.168.1.3:3817	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3873	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3877	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3881	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3890	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3895	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3904	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3908	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3913	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3921	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3925	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3937	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3945	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3949	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3954	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3962	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3966	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3970	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3974	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3982	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:3987	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:4565	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:4568	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:4572	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:4576	10.0.0.154:41144	CLOSE_WAIT	
    ts3client_win32.exe:2544	TCP	192.168.1.3:4584	10.0.0.154:41144	CLOSE_WAIT	
    vmware-authd.exe:1316	TCP	0.0.0.0:912	0.0.0.0:0	LISTENING
    Of the two bookmarks I use to connect to the virtual server, one is just the straight IP address, and the second is the tsdns domain name

    Let me know if you need more information.

    And congratulations on the final release of 3.0.0

  2. #2
    Join Date
    Jul 2002
    Location
    Germany
    Posts
    2,836
    Hey,

    the CLOSE_WAIT connections are normal and nothing bad (you get the same if you browse a little with your web browser). Are you experiencing any bug/issue?
    You think my answer is stupid ? Read This:
    http://www.catb.org/~esr/faqs/smart-...ons.html#intro

    In a world without fences and walls - who needs windows and gates ?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 3
    Last Post: 18-07-2011, 16:00
  2. Multiple Channel connections by same client
    By VonRC in forum General Questions
    Replies: 2
    Last Post: 15-02-2011, 06:43
  3. server/client probllem (ip connections)
    By djjamieb in forum General Questions
    Replies: 4
    Last Post: 06-02-2011, 20:02
  4. Replies: 2
    Last Post: 19-06-2010, 20:32
  5. 1 client = 3 simultaneous connections
    By areyna in forum Permission System
    Replies: 1
    Last Post: 26-01-2010, 13:00

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •