Failed to connect to server

[Luftwalk]

Hi,

I'm using TS3 server with the NPL license on a Debian server. I've followed directions on installing the server on this thread: http://forum.teamspeak.com/showthrea...-Debian-Ubuntu

The installation went fine and the server starts without problems. Ports are opened as well and the server is listening on them:

root@mx:/home/teamspeak/tsserver/teamspeak/logs# netstat -lnp | grep ts3
tcp        0      0 0.0.0.0:30033           0.0.0.0:*               LISTEN      8824/ts3server_linu
tcp        0      0 0.0.0.0:10011           0.0.0.0:*               LISTEN      8824/ts3server_linu
udp        0      0 0.0.0.0:9987            0.0.0.0:*                           8824/ts3server_linu

When I try to connect to the server using the client it resolves the dns name and then fails to connect. I can connect to other servers ok.

Server address is: inner-core.info (IP: 91.240.216.253)
Port is the default: 9987

This is the client log:

13.9.2012 16:46:28	ClientUI	Info	Connect to server: www.inner-core.info	
13.9.2012 16:46:28	ClientUI	Info	Trying to resolve www.inner-core.info	
13.9.2012 16:46:28		Info	DNS resolve successful, "www.inner-core.info"=91.240.216.253	
13.9.2012 16:46:28		Info	SRV DNS resolve unsuccessful for "_ts3._udp.www.inner-core.info"	
13.9.2012 16:46:29	ClientUI	Info	Lookup finished: 91.240.216.253 9987 www.inner-core.info 0 0	
13.9.2012 16:46:29	ClientUI	Info	Resolve successful: 91.240.216.253:9987	
13.9.2012 16:46:29	ClientUI	Info	Blacklist check ok	
13.9.2012 16:46:29	ClientUI	Info	Initiating connection: 91.240.216.253:9987 www.inner-core.info	
13.9.2012 16:46:29	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - enter	
13.9.2012 16:46:29	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - leave	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS::openDevice-enter	
13.9.2012 16:46:29		Info	DNS resolve successful, "blacklist.teamspeak.com"=80.190.225.139	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS Buffer size: 1323	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS::openDevice-leave	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS::startDevice-enter	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS::startDevice-leave	
13.9.2012 16:46:29	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - enter	
13.9.2012 16:46:29	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - leave	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS::openDevice-enter	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS Buffer size: 882	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS::openDevice-leave	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS::startDevice-enter	
13.9.2012 16:46:29	Windows Audio Session	Debug	WAS::startDevice-leave	
13.9.2012 16:46:29	ClientUI	Info	Connect status: Connecting	
13.9.2012 16:46:35	ClientUI	Info	Connect status: Disconnected	
13.9.2012 16:46:35	ClientUI	Info	Failed to connect to server, want autoreconnect = 0

If anyone has any clues I'd be really grateful.

[ARCHI]

Please post there your latest server logs located in your /logs/ directory on the server. _0.log and _1.log

Thank you.

[Luftwalk]

Please post there your latest server logs located in your /logs/ directory on the server. _0.log and _1.log

Thank you.

Here they are:

012-09-13 14:38:17.153839|INFO    |ServerLibPriv |   | TeamSpeak 3 Server 3.0.6.1 (2012-06-29 07:59:05)
2012-09-13 14:38:17.155112|INFO    |DatabaseQuery |   | dbPlugin name:    MySQL plugin, (c)TeamSpeak Systems GmbH
2012-09-13 14:38:17.155151|INFO    |DatabaseQuery |   | dbPlugin version: 1
2012-09-13 14:38:17.394131|INFO    |Accounting    |   | Licensing Information
2012-09-13 14:38:17.394193|INFO    |Accounting    |   | type              : Non-profit
2012-09-13 14:38:17.394249|INFO    |Accounting    |   | starting date     : Wed Sep 12 00:00:00 2012
2012-09-13 14:38:17.394282|INFO    |Accounting    |   | ending date       : Tue Mar 12 00:00:00 2013
2012-09-13 14:38:17.394309|INFO    |Accounting    |   | max virtualservers: 10
2012-09-13 14:38:17.394334|INFO    |Accounting    |   | max slots         : 512
2012-09-13 14:38:17.413191|INFO    |FileManager   |   | listening on 0.0.0.0:30033
2012-09-13 14:38:18.270687|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1,
2012-09-13 14:38:18.271072|INFO    |Query         |   | listening on 0.0.0.0:10011

and the latest:

2012-09-13 14:38:18.270519|INFO    |VirtualServer |  1| listening on 0.0.0.0:9987

[ARCHI]

Logs are fine.

There isn't any issue with TS3 Server.

You can only check if process is running. Execute ps ax | grep ts3server and check if ts3server_linux_x86/amd64 is there.

If you can see it then server is up and running. If not then process is dead for some reason.

If process is up then you can check your firewall or network settings because it's definitely not a problem of server configuration. You would get errors in logs then.

You can also execute netstat -vaun and check if your server is listening on :9987 port. You should be able to see such record.

[Luftwalk]

I get this with the ps ax command:

3731 pts/1    S+     0:00 grep ts3server
 8804 ?        S      0:00 su teamspeak -c /home/teamspeak/tsserver/teamspeak/ts3server_minimal_runscript.sh inifile=ts3server.ini
 8806 ?        S      0:00 /bin/sh /home/teamspeak/tsserver/teamspeak/ts3server_minimal_runscript.sh inifile=ts3server.ini
 8824 ?        Sl     3:44 ./ts3server_linux_amd64 inifile=ts3server.ini

is there an issue with there being 3 entries or is the only important one the last one?

Netstat does return the line for the 9987 port:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
udp        0      0 91.240.216.253:53       0.0.0.0:*
udp        0      0 91.240.216.140:53       0.0.0.0:*
udp        0      0 127.0.0.1:53            0.0.0.0:*
udp        0      0 91.240.216.140:60344    194.97.114.3:2010       ESTABLISHED
udp        0      0 0.0.0.0:68              0.0.0.0:*
udp        0      0 0.0.0.0:9987            0.0.0.0:*
udp6       0      0 :::53                   :::*

Thanks for all the help.

[Luftwalk]

This is odd. I tried checking the server status and it returned this:

teamspeak@mx:~/tsserver/teamspeak$ ./ts3server_startscript.sh status
No server running (ts3server.pid is missing)

This doesn't make sense. Using the top command I can see the ts3_server process. Any idea what's going on?

[Luftwalk]

After using the startscript.sh to start the server instead of the minimal runscript I get this with the ps and netstat commands:

root@mx:/home/teamspeak/tsserver/teamspeak# ps ax | grep ts3server
 5818 pts/1    Sl     0:01 ./ts3server_linux_amd64 inifile=ts3server.ini
 6468 pts/1    S+     0:00 grep ts3server

root@mx:/home/teamspeak/tsserver/teamspeak# netstat -vaun
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
udp        0      0 91.240.216.253:53       0.0.0.0:*
udp        0      0 91.240.216.140:53       0.0.0.0:*
udp        0      0 127.0.0.1:53            0.0.0.0:*
udp        0      0 0.0.0.0:68              0.0.0.0:*
udp        0      0 91.240.216.140:53627    194.97.114.3:2010       ESTABLISHED
udp        0      0 0.0.0.0:9987            0.0.0.0:*
udp6       0      0 :::53                   :::*
root@mx:/home/teamspeak/tsserver/teamspeak#

Server status now says the server is running but I still fail to connect to it.

[Luftwalk]

Ok,

I seem to have resolved the issue. I used my server's IP in the ini file insted of 0.0.0.0 and I could connect to the server.
Any idea why this is so?

[ARCHI]

Minimal runscript just starts TS3 Server as process, it's just like starting a single process under windows.

Startscript creates "process instance" - creating .pid file and starting process itself (like runscript). You can't check status of startscript without it. I mean you can start server in both ways but using first way you can't use startscript status command because it won't detect it.

[Chris]

If the server has more than 1 ip address the TeamSpeak server will be listening on both and also answer with a random address which will result in you not getting the answer since it came from an ip address you did not establish a connection to, thus these packets get dropped.