TS server crash on kernel 2.6.16.14 SMP

[bruce]

We have been successfully running teamspeak on a Linux-Vserver Virtual Server for some time. We just moved to a new server (dual p4 2.8 with kernel 2.6.16.14 SMP), using the same 'vps image' as before but TS locks up.

How it happens?

TS starts sucessfully. People can connect to it. After some time everyone times out, the connection ont he tcp port is "accepted" but not answered. A 'ps' shows all processes are active and seem to be ok. This is not a network issue since a restart on ts makes it work again.
This is happening a lot, like once an hour.

An strace on the active processes repeats this:
=================================
select(23, [22], [], [], {0, 100000}[{fd=13, events=POLLIN}], 1, 52) = 0
gettimeofday({1149605956, 472366}, NULL) = 0
gettimeofday({1149605956, 472414}, NULL) = 0
poll() = 0 (Timeout)
=================================

This is not related to the instalation, since moving this VPS to another machine with a different kernel makes it work perfectly.

We are almost sure this is a TS bug. Any help would be appreciated.

Thanks in Advance

[bruce]

Any ideas?

[ScP]

Which version of the TeamSpeak 2 server do you use?

[bruce]

I use ts2_server_rc2_20201 (2.0.20.1). I've also tried the 2.0.22.3 BETA but it gives the same result (random lockups).

As a workaround, which is not giving us success, we made a shell script with 'netcat' that sends a udp string to teamspeak's UDP port and waits for an answer. When there is no answer in 10 seconds the script restarts teamspeak. At least with this we don't have to restart it manually :)

This script makes a log file of all lockup it finds (13 last hour, sometimes it doesn't lockup for 2 hours). If it is relevant i can post it here.

The only differences from the old server (the linux image is the same, the vps was migrated) are the processor (old one was celeron, this one is dual core p4) and kernel (old one was 2.6.15.4, this one is 2.6.16.14).

There are no firewall rules related to this ip or port, nor "mangle" rules. If it was a firewall issue, restarting teamspeak wouldn't make it work again.

Thanks for you atention.

[Johno]

try starting your ts server with the setarch command; something like.. setarch <arch> -L ./teamspeak2-server_startscript start

[bruce]

Just tried setarch without success.