HELP! Second server instance randomly dies / times out..

[motivez]

I set up a second instance of the TeamSpeak server according to the directions listed here:

http://www.teamspeak.com/?page=tutorial_c

Changed the UDP port (8888), the HTTP server (33011) / TCP Query (34011) ports, etc.. to something different than the original server.

The server starts fine and runs for awhile, but after a time, it simply times out and no one can connect to it. Can't connect to the web interface to restart the server either, meaning I need to go into the server, kill the process, remove the pid file, and restart the server manually.

This is annoying for me, but also for the people I'm running the server for.. as it should be far more stable than it is currently.

The other instance of the server I have stays up and running 24/7 and I'm not having any issues with it.. so I really don't know what the deal is here.

Anyone have any ideas?

Thanks

[ANR Daemon]

Sure you have that said second server started from different installation, or do they both share the same directory?

[motivez]

I originally installed the second server in another directory to keep them both separate so the server admin's wouldn't have access to the other server instance

However, I decided maybe there was some kind of conflict with that, and created / launched the second server from the web interface of the first

Still the same issue, after some time one of the servers will time out

Here's the server.log:


---------------------------------------------------------------
-------------- log started at 19-01-09 01:05 -------------
---------------------------------------------------------------
19-01-09 01:05:10,ALL,Info,server, Server init initialized
19-01-09 01:05:10,ALL,Info,server, Server version: 2.0.20.1 Linux
19-01-09 01:05:10,ALL,Info,server, Starting VirtualServer id:1 with port:8767
19-01-09 01:05:10,ALL,Info,server, Starting VirtualServer id:2 with port:7777
19-01-09 01:05:10,ALL,Info,server, Server init finished
19-01-09 01:05:10,WARNING,Info,server, TeamSpeak Server daemon activated
19-01-09 01:07:59,ALL,Info,server, Starting VirtualServer id:2 with port:7777
---------------------------------------------------------------
-------------- log started at 19-01-09 03:54 -------------
---------------------------------------------------------------
19-01-09 03:54:12,ALL,Info,server, Server init initialized
19-01-09 03:54:12,ALL,Info,server, Server version: 2.0.20.1 Linux
19-01-09 03:54:13,ALL,Info,server, Starting VirtualServer id:1 with port:8767
19-01-09 03:54:13,ALL,Info,server, Starting VirtualServer id:2 with port:7777
19-01-09 03:54:13,ALL,Info,server, Server init finished
19-01-09 03:54:13,WARNING,Info,server, TeamSpeak Server daemon activated

I just downloaded the updated binary and restarted the servers:


---------------------------------------------------------------
-------------- log started at 19-01-09 04:09 -------------
---------------------------------------------------------------
19-01-09 04:09:48,ALL,Info,server, Server init initialized
19-01-09 04:09:48,ALL,Info,server, Server version: 2.0.24.1 Linux
19-01-09 04:09:48,ALL,Info,server, Starting VirtualServer id:1 with port:8767
19-01-09 04:09:48,ALL,Info,server, Started VirtualServer id:1 with port:8767
19-01-09 04:09:48,ALL,Info,server, Starting VirtualServer id:2 with port:7777
19-01-09 04:09:48,ALL,Info,server, Started VirtualServer id:2 with port:7777
19-01-09 04:09:49,ALL,Info,server, Server init finished
19-01-09 04:09:49,WARNING,Info,server, TeamSpeak Server daemon activated

Any idea why the server instances are doubled there?

Is there any flag in the server.ini for more rigorous logging / debug options?

[motivez]

Hrm.. Well the updated binary didn't help out apparently.


[07:52:10] Connecting to x:7777
[07:52:10] Connected to server Teamspeak
[07:52:10] Welcome to the TeamSpeak server
[07:59:19] Connection timed out


The web interface is down as well.. yet the processes are still running on the server:


[motivez@x ~/teamspeak]$ ps ux | grep server_linux
motivez 61697 0.0 0.3 29356 3100 p1 SN 4:09AM 0:00.54 ./server_linux -PID=tsserver2.pid
motivez 61698 0.0 0.3 29356 3100 p1 SN 4:09AM 0:00.02 ./server_linux -PID=tsserver2.pid
motivez 61699 0.0 0.3 29356 3100 p1 IN 4:09AM 0:01.96 ./server_linux -PID=tsserver2.pid
motivez 61700 0.0 0.3 29356 3100 p1 IN 4:09AM 0:01.49 ./server_linux -PID=tsserver2.pid
motivez 61701 0.0 0.3 29356 3100 p1 SN 4:09AM 0:00.31 ./server_linux -PID=tsserver2.pid
motivez 61702 0.0 0.3 29356 3100 p1 IN 4:09AM 0:01.77 ./server_linux -PID=tsserver2.pid
motivez 61703 0.0 0.3 29356 3100 p1 IN 4:09AM 0:01.67 ./server_linux -PID=tsserver2.pid
motivez 61704 0.0 0.3 29356 3100 p1 IN 4:09AM 0:00.16 ./server_linux -PID=tsserver2.pid
motivez 61705 0.0 0.3 29356 3100 p1 SN 4:09AM 0:00.04 ./server_linux -PID=tsserver2.pid
motivez 61706 0.0 0.3 29356 3100 p1 SN 4:09AM 0:01.10 ./server_linux -PID=tsserver2.pid
motivez 61707 0.0 0.3 29356 3100 p1 SN 4:09AM 0:01.09 ./server_linux -PID=tsserver2.pid
motivez 61708 0.0 0.3 29356 3100 p1 SN 4:09AM 0:00.10 ./server_linux -PID=tsserver2.pid
motivez 65469 0.0 0.3 29356 3100 p1 IN 5:00AM 0:00.00 ./server_linux -PID=tsserver2.pid

[motivez]

Here's the log from my client in debug mode:



---------------------------------------------------------------
-------------- log started at 19-01-09 06:47 -------------
---------------------------------------------------------------
19-01-09 06:47:33,4176,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
19-01-09 06:47:33,3292,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
19-01-09 07:09:48,5388,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
19-01-09 07:09:49,5388,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
19-01-09 07:09:50,5388,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
19-01-09 07:09:51,5388,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
19-01-09 08:05:02,4176,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
19-01-09 08:05:02,3292,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."


Any idea?

[motivez]

[09:21:36] Connecting to x:7777
[09:21:36] Connected to server Teamspeak
[09:21:36] Welcome to the TeamSpeak server
[09:50:33] Connection timed out


19-01-09 09:50:33,3948,DEBUG,All,TClient.CloseCon,enter
19-01-09 09:50:33,3948,DEBUG,All,TClient.CloseCon,active enter
19-01-09 09:50:33,3948,DEBUG,All,TClient.CloseCon,active Send close
19-01-09 09:50:33,2420,DEBUG,All,cb_close,close callback enter
19-01-09 09:50:33,2420,DEBUG,All,cb_close,close callback leave
19-01-09 09:50:33,3948,DEBUG,All,TClient.CloseCon,active UDP closed
19-01-09 09:50:33,3948,DEBUG,All,TClient.CloseCon,active cleared nodes
19-01-09 09:50:33,3948,DEBUG,All,TClient.CloseCon,active leave
19-01-09 09:50:33,3948,DEBUG,All,TClient.CloseCon,leave


Argh!

Anyone?

[motivez]

Oh, and I should point out that now both servers are dying.. not simply the second instance.

[motivez]

Again..

19-01-09 18:01:00,3948,DEBUG,All,TClient.CloseCon,enter
19-01-09 18:01:00,2420,DEBUG,All,cb_close,close callback enter
19-01-09 18:01:00,3948,DEBUG,All,TClient.CloseCon,active enter
19-01-09 18:01:00,3948,DEBUG,All,TClient.CloseCon,active Send close
19-01-09 18:01:00,2420,DEBUG,All,cb_close,close callback leave
19-01-09 18:01:00,3948,DEBUG,All,TClient.CloseCon,active UDP closed
19-01-09 18:01:00,3948,DEBUG,All,TClient.CloseCon,active cleared nodes
19-01-09 18:01:00,3948,DEBUG,All,TClient.CloseCon,active leave
19-01-09 18:01:00,3948,DEBUG,All,TClient.CloseCon,leave
19-01-09 18:01:16,2420,DEBUG,ProcedureInfo,Client Open,host 69.xx resolved to 69.xx
19-01-09 18:01:16,2420,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
19-01-09 18:01:16,2420,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
19-01-09 18:01:19,2420,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
19-01-09 18:01:19,5748,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."

Anyone?

[motivez]

Again, died today:

21-01-09 12:04:21,2688,DEBUG,All,cb_close,close callback enter
21-01-09 12:04:21,816,DEBUG,All,TClient.CloseCon,enter
21-01-09 12:04:21,816,DEBUG,All,TClient.CloseCon,active enter
21-01-09 12:04:21,816,DEBUG,All,TClient.CloseCon,active Send close
21-01-09 12:04:21,2688,DEBUG,All,cb_close,close callback leave
21-01-09 12:04:21,816,DEBUG,All,TClient.CloseCon,active UDP closed
21-01-09 12:04:21,816,DEBUG,All,TClient.CloseCon,active cleared nodes
21-01-09 12:04:21,816,DEBUG,All,TClient.CloseCon,active leave
21-01-09 12:04:21,816,DEBUG,All,TClient.CloseCon,leave


Is there any official support around here or what?

[motivez]

Not even 1 reply from someone? Is this project even still alive?

[motivez]

I'm pretty sure I've narrowed this down to running multiple servers.. which is odd, since I thought TeamSpeak was designed to easily handle multiple servers on the same account / same installation. Apparently not.

In any case, what seems to be happening is:

Regardless of whether the second server is a completely separate install in its own directory, or created and started from within the web interface of the first server.. the servers will both simply die after a time period and be completely unconnectable.

To test, I started both servers using the second method (created #2 from the web interface of #1) and left them running.

At the same time, I launched a second server on a separate account with different ports selected and let it run.

The first set of servers continues to die after a time, while the second one has been up for several days now.

I'm willing to help debug this if anyone from the TeamSpeak team actually cares.