[Ts2] Windows/Linux Server Binary BETA 2.0.23.6

ScP · #1 25-09-2006, 09:15

Hi there,

We've released a new TeamSpeak 2 server binary for Linux and Windows today.

The new version deals with the following issues:

- fixed a critical bug from version 2.0.23.5, that can cause a virtual server to become completely unresponsive

Please note that this version also contains all bugfixes that were previously released in Linux and Windows binaries (2.0.21.3, 2.0.22.1, 2.0.22.2, 2.0.22.3, 2.0.23.2 and 2.0.23.5).

You can find the new release on our Downloads page.

dsc_chris · #2 25-09-2006, 15:10

ScP,

Is there a way to slow down how fast the server starts when using mysql, I know the mysql stuff is a major Beta. Just recently when I started using the new beta releases I noticed you guys now log the output from mysql on errors and I notice that if there are a lot of servers mysql tends to get flooded and kill the connection which causes virtual servers to not start up at all.

I am pretty sure I have maxed out my settings in mysql. Any assistance would be great, or even a way to limit how fast the queries get sent to mysql maybe do 1 query a second or something. That would help out ALOT even though this is still beta.

dsc_chris · #3 25-09-2006, 20:34

ScP,

Also, a new possible bug. Servers are randomly just stopping.

R. Ludwig · #4 26-09-2006, 05:25

Quote:

Originally Posted by dsc_chris

ScP,

Also, a new possible bug. Servers are randomly just stopping.

more details please! how to reproduce etc etc.

ScP · #5 26-09-2006, 08:15

Quote:

Originally Posted by dsc_chris

... Any assistance would be great, or even a way to limit how fast the queries get sent to mysql maybe do 1 query a second or something ...

Unfortunately, this is not possible by editing the settings of your TeamSpeak 2 server. Maybe there's a setting or a command to realize this on the MySQL servers side.

As Ralf already said, we need more information about this possible bug. Your servers log and configuration files, your MySQL version and your OS (including kernel version and patchset) could be useful.

Thanks in advance!

dsc_chris · #6 26-09-2006, 14:54

Good Morning Ralph and ScP,

Did some testing last night to try and track the bug down, found out that when one of our scripts called the stopserver function without specifying the server id once in a while it will stop every server on the daemon and once in a while it will not. I have corrected our script for the time being to send a specific server id but this was perfectly fine before this with no issues so I figure this is a bug.

Another thing I noticed, I do like how it now outputs the mysql errors to the log file. In the 2.0.20.1 software I was able to load at least 100 or so virtual servers, now I am not even able to load this many as it starts giving disconnecting from mysql. I have checked for any possible mysql misconfigurations and I dont believe I am finding any. I have checked mysql's site for any query flood protection but from my understanding mysql queues queries.

Unfortunately if I can't get the virtual servers to load like in 2.0.20.1 I may have to go back to an older version.

I also tried using mysql 3, that had so many errors it didnt like the sql queries being sent to it I had to go up to 4.0. I do understand mysql is in beta so I am not tripping too much but sadly mysql is the only feasible sql platform for our systems since sqlite we cant write to the file when teamspeak is using it.

dsc_chris · #7 26-09-2006, 15:24

Found a new bug.

We create servers via the TCP Query System. We have a server which is online and running however it is not listed in the teamspeak control panel yet we can connect to it.

There is a new server which is created but has 0 slots and has a default port with no server name.

ScP · #8 26-09-2006, 20:16

Quote:

Originally Posted by dsc_chris

... when one of our scripts called the stopserver function without specifying the server id once in a while it will stop every server on the daemon and once in a while it will not ...

That's weird, because the serverstop command does not support any parameters. You have to select the virtual server first. Here's an example:

Code:

dbserverlist
id   udpport   name
1    8767      "TeamSpeak Public  -1-"
sel 8767
OK
serverstop
OK

Referring to your second concern, I'd recommend that you check the official server farming recommendations on our System Requirements page.

As I already said, your servers log and configuration files, your MySQL version and your OS (including kernel version and patchset) could be useful.

dsc_chris · #9 26-09-2006, 21:07

ScP,

I can send you the logs -- your right the serverstop does not take parameters I was looking at serverstart. We are still having the issue with daemons just stopping after one client clicks Stop on his server, our code has not changed since we built the system and now suddenly it does this.

I will PM you a copy of the log as it has IP's and such.

ScP · #10 28-09-2006, 07:36

@dsc_chris:
We've received your servers logfile now. I think the problem here is, that you're running more than 150 virtual servers in a single TeamSpeak 2 server instance. Due to our server farming recommendations, you should never setup more than 75 virtual servers per instance (running binary).

We'd strongly recommend, that you split up your database. This should fix your problems and increase the servers performance. Please feel free to contact us by email, if we can assist you on any matter.

Vashji · #11 28-09-2006, 22:21

does this version work with MySQL? every one says MySQL with teamspeak is in beta. But with 2.0.20.1 it works fine.

dsc_chris · #12 29-09-2006, 05:37

Ralph,

I understand the server farming idea, had you had that posted when we first became an ATHP it would have helped. We switched over to windows and actually you can get away with around 150 virtual servers. However we don't have problems until we hit around 300 to 400 servers. Since you guys are releasing small updates, why dont you fix the minor issues with mysql and bump up the "recommended" limit so that way AHTP's can farm servers a bit more streamlined.

I guess really this will not affect us, we have switched to a bit of a different way of provisioning our servers as of the last few days due to the excessive issues with the TS Server software.

Thomas · #13 29-09-2006, 22:00

Why don't you start more than one TeamSpeak-Servers on the root-Server?

It's really hard for the server to manage 400 virtual TeamSpeak-Servers.

dsc_chris · #14 29-09-2006, 22:03

PLuS,

We actually have a system which manages all the servers and makes it very easy on us

Thomas · #15 29-09-2006, 23:06

Uups, sorry, I didn't see the word "not" in

Quote:

However we don't have problems

It's too late, I will be quiet till tomorrow! :P