TeamSpeak 3 Server 3.0.0-beta16 Available

[Peter]

We've just finished uploading version 3.0.0-beta16 of the server. Here's a list of changes:

=== Server Release 3.0.0-beta16 20 Jan 2010
- default query anti flood properties changed to be less strict
- added warning while using machine_id and no servers got loaded
- fixed possible exception in query core on certain linux derivates
+ query_ip_whitelist.txt auto reloads every five minutes
  entries are displayed to logfile, first time and every time they changed
  while reloading
+ reduce memory usage
+ shut down server cleanly on unix systems even when receiving SIGINT,
  SIGHUP and SIGTERM

Have fun downloading

[Jonybat]

Up and running...

Thanks

[serano]

downloading. Waiting for client update aswell


EDIT: installed and running.

[Hiigara]

up and running, no problems so far (smaller memory footprint and cpu usage compared to beta15)

[Desperate55]

I have now 3.0.0-beta7 [Build: 9514] so if i want update server to version 16 i must overwrite all old files with new.Can any 1 tell me what more i must do?I think i use sql cuz it's default and i didn't change anything.

[serano]

First problem found.

The Teamspeak Server Linux beta 16 now receives SIGHUP signals when using: nohup ./ts3_linux_x86 . Trying to find a workaway around.

[Jonybat]

I have now 3.0.0-beta7 [Build: 9514] so if i want update server to version 16 i must overwrite all old files with new.Can any 1 tell me what more i must do?I think i use sql cuz it's default and i didn't change anything.

All you have to do is stop the server, backup the ts3server.sqlitedb (just to be safe), overwrite all the server files with the new ones and start the server again.

Then, there are some lines to insert in sql (no one ever said if we really had to or not), but since you come from beta 7, that should not limit your server functionalities.

[TCXVirtual]

It's getting a bit of a pain now, because my server is constanty recieving SIGHUP regardless of "nohup" being used.


This is why my nohup.out looks like:

Logging started
2010-01-22 21:52:09.491929|INFO |ServerLibPriv | | Server Version: 3.0.0-be ta16 [Build: 9929]
2010-01-22 21:52:09.493822|INFO |DatabaseQuery | | dbPlugin name: MySQL plugin, (c)TeamSpeak Systems GmbH
2010-01-22 21:52:09.493860|INFO |DatabaseQuery | | dbPlugin version: 1
2010-01-22 21:52:09.674692|WARNING |Accounting | | Unable to find valid lic ense key, falling back to limited functionality
2010-01-22 21:52:09.686491|INFO |FileManager | | listening on 0.0.0.0:300 33
2010-01-22 21:52:09.712031|INFO |VirtualServer | 1| listening on 0.0.0.0:998 7
2010-01-22 21:52:09.712571|INFO |Query | | listening on 0.0.0.0:100 11
2010-01-22 21:52:09.802335|INFO |Query | | whitelist ips: 127.0.0.1 ,
2010-01-23 00:13:16.974344|INFO |ServerMain | | Received signal SIGHUP, shutting down.
2010-01-23 00:13:17.301679|INFO |VirtualServer | 1| stopped
TeamSpeak Server 3.0.0-beta16 [Build: 9929]

This is what command I run:

[root@usa1 teamspeak3-server_linux-x86]# cd /var/www/teamspeak/teamspeak3-server_linux-x86/
[root@usa1 teamspeak3-server_linux-x86]# nohup ./ts3server_linux_x86 inifile=ts3server.ini &

All help appreciated,
cheers,
Dom.

[Jerry]

It's getting a bit of a pain now, because my server is constanty recieving SIGHUP regardless of "nohup" being used.

Have exactly the same problem with using nohup.

[bad_dud]

Have exactly the same problem with using nohup.

Try to use this after you have cd to your directory it works for me on a fedora box.

./ts3server_linux_x86 inifile=ts3server.ini > /dev/null 2>&1 &

To make autostart when you restart the server iam using that row in a script file.
Add a user to run it and add like this to your rc.local file in etc/rc.d

su - USER -c ./start_ts3

[Jerry]

Try to use this after you have cd to your directory it works for me on a fedora box.

./ts3server_linux_x86 inifile=ts3server.ini > /dev/null 2>&1 &

To make autostart when you restart the server iam using that row in a script file.
Add a user to run it and add like this to your rc.local file in etc/rc.d

su - USER -c ./start_ts3

Thanks for advise pal, work like a charm with centos

[Peter]

screen
cd ts3folder
./ts3server_linux_amd64
[ctrl+a, d] <--- pressing this will detach you from the screen
you can now exit your shell...

If you want to "check up" on your ts3 server, log back on and do:
screen -r

[FSchroeder]

I have the following problem.

Today I installed a new instance. I wondered, because my ts viewer and a part of the interface do not work fine as before. After a short time I found out, that the template guest query group was changed. Maybe I skip it in the changelog, but its pretty dumb to change the template guest group at the moment.

I think the change come with beta 15 or 16. After an install of beta12 all works fine.

In my mind, the actual template of the guest query group is a very bad one. Because, every hoster shoul edit the group anyway, because of ts-viewer.com and other viewers.