PDA

View Full Version : Server Connection Woes


davisford
21-01-2004, 06:28
Hi, here is some basic info on my setup

Client Version:
TeamSpeak 2 2.0.32.60 (windows)
Server Version: ts2_server_rc2_201916 (linux)

The connection is over LAN. There are no IP/Router issues.

The problem in a nutshell is that once initially connected, if I disconnect and try to reconnect, I cannot do so. Now I appear to be completely locked out of ever connecting either via anonymous or registered mode.

When I try to connect to the server, the client reports:

[00:07:20] Connection timed out

In the client logfile:

21-01-04 00:07:18,2028,DEBUG,ProcedureInfo,Client Open,host 192.168.1.10 resolved to 192.168.1.10
21-01-04 00:07:18,2028,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
21-01-04 00:07:18,2028,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
21-01-04 00:07:18,2028,DEBUG,ProcedureInfo,Client Open,LoginStep2 received
21-01-04 00:07:18,2028,DEBUG,ProcedureInfo,Client Open,Sending LoginStep3
21-01-04 00:07:18,2028,DEBUG,All,cb_connecting,connecting callback
21-01-04 00:07:20,2720,DEBUG,All,TClient.CloseCon,enter
21-01-04 00:07:20,2720,DEBUG,All,TClient.CloseCon,active enter
21-01-04 00:07:20,2028,DEBUG,All,cb_close,close callback enter
21-01-04 00:07:20,2720,DEBUG,All,TClient.CloseCon,active Send close
21-01-04 00:07:20,2028,DEBUG,All,cb_close,close callback leave
21-01-04 00:07:20,2720,DEBUG,All,TClient.CloseCon,active UDP closed
21-01-04 00:07:20,2720,DEBUG,All,TClient.CloseCon,active cleared nodes
21-01-04 00:07:20,2720,DEBUG,All,TClient.CloseCon,active leave
21-01-04 00:07:20,2720,DEBUG,All,TClient.CloseCon,leave

From the server.log file on the server:

21-01-04 00:11:05,ALL,Info,AccessLog, client connected [IP: 192.168.1.4, Nick: Davis, LoginName: davis]
21-01-04 00:11:35,ALL,Info,AccessLog, client timed out. [Nick: Davis]

The server.ini file is thus:

[debug]
MessageTypes=LMTALL
MessageDepths=LMDALL

[Main Config]
ExternalIPDectection=1
HTTPServer Port=14534
HTTPServer Enabled=1
DateTimeFormat=dd-mm-yyyy hh:nn:ss
TCPQueryPort=51234
BoundToIp=

[WebPost]
AdminEmail=na
ISPLinkURL=na
ISPName=Private
ISPCountry=Earth
Enabled=0
PostURL=
ListPublic=0

[ISP]
GFX URL=

[log]
access=1

I can login to the website, and I can login to the telnet query.

When I login as superadmin to the telnet query, I see that even though my client cannot connect, doing a "pl" command shows I am connected briefly.
If I repeat the "pl" command it will go away eventually.

pl
1 1 42 19874 5 288 0 41 3 3 0 5 0 192.168.1.4 Davis davis

The "checkserverok" returns:
checkserverok
OK

ver
2.0.19.16 Linux
OK

si
server_id=1
server_name=TeamSpeak
server_platform=Linux
server_welcomemessage=[Welcome to TeamSpeak, check www.teamspeak.org]
server_webpost_linkurl=
server_password=1
server_udpport=8767
server_maxusers=8
server_codeccelp51=-1
server_codeccelp63=-1
server_codecgsm148=-1
server_codecgsm164=-1
server_codecwindowscelp52=-1
server_packetssend=3053
server_bytessend=1524136
server_packetsreceived=35
server_bytesreceived=2436
server_uptime=1974
server_currentusers=0
server_currentchannels=9
server_bwinlastsec=0
server_bwoutlastsec=1673
server_bwinlastmin=0
server_bwoutlastmin=0
OK

Unfortunately, stopping and starting the server via telnet, or by killing the process -HUP, or by -9 and restarting the process manually or via the scripts -- still does not solve the problem. Killing the client as well does no good.

It seems the database perhaps has been corrupted? But I have no way to tell.

I tried earlier this evening upgrading to
ts2_server_rc2_201940 and that was actually worse. So, I downgraded to ts2_server_rc2_201916 The problems I was having were that I could connect successfully *once* -- after which if I disconnected and tried to reconnect, it started complaining about the user already being logged in...here is a sample from server.log:

20-01-04 23:32:42,ALL,Info,server, Server init initialized
20-01-04 23:32:42,ALL,Info,server, Server version: 2.0.19.16 Linux
20-01-04 23:32:43,ALL,Info,server, Starting server with port: 8767
20-01-04 23:32:44,ALL,Info,server, Server init finished
20-01-04 23:32:44,WARNING,Info,server, TeamSpeak Server daemon activated
20-01-04 23:32:52,ALL,Info,AccessLog, client connected [IP: 68.43.239.224, Nick: Onno, LoginName: ohommes]
20-01-04 23:33:04,ALL,Info,AccessLog, client disconnected, reason LoginName in use [IP: 68.43.239.224, Nick: Onno, LoginName: ohommes]

For awhile there, killing the process, and restarting seemed to make things work again. Now, however, I cannot log in at all. Something has gone terribly wrong. Can anyone point me to some tips for what I can do to solve this problem?

Just a recap -- I did have the client/server speaking successfully and was having conversation with multiple Internet clients. Then whenever a client would disconnect and try a reconnect, they could not get back in b/c it said their username was already logged in (including me on the local LAN). This further progressed into not being able to login at all no matter how many times we restarted the server or client processes.

The client and server I am running are both the same hardware but different operating systems (Win2K vs. GNU/Linux 2.4.20-28.9smp)

Hardware is Dual-CPU Pentium III 1.13 GHz, 2GB SDRAM, Gigabit Ethernet

Thanks in advance,
Davis

davisford
21-01-2004, 06:54
One more piece of info.

I deleted the server.dbs file, and then restarted the server, and lo and behold the problems disappeared -- well, I could at least log in again. As suspected, the database somehow got corrupted.

My question is *why* did the database get corrupted, and how can I prevent this in the future?

Deleting the .dbs file is not all that friendly of a fix b/c it means I have to go in and recreate users and permissions and channels each time I recreate the .dbs file.

Any help is greatly appreciated..

Thanks in advance,

Davis

Dummer Sack
21-01-2004, 14:56
Since there are many possibilites why that db maybe got currupted and I don't know how it happened I can only suggest to backup frequently.

Or upgrade to server b50 and use mysql as db. With that you may have more security against db corruption.