TeamSpeak 3 Server 3.0.0-beta17 Available

[R. Ludwig]

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

=== Server Release 3.0.0-beta17 02 Feb 2010
- fixed possible crash while deleting subchannels
- clientlist option -VOICE added CLIENT_IS_PRIORITY_SPEAKER property
- fixed issue where query could start an stopped virtualserver while
  instance terminating
- fixed channel_flag_password was not set automatically while creating
  a new channel over query  
- fixed strange behavior while changing b_group_is_permanent permission value
- fixed licensing issue with max slots below 32
- query_ip_whitelist.txt removed out of package and is created if not available
- fixed PERMISSION_b_client_channel_textmessage_send not working properly
- fixed ghosting channel bug with certain default sub channel setups
- fixed critical after editing an perm/semi channel to an temp
- fixed unclear local accounting error messages
- fixed query bug which resulted in "invalid socketID" errors
+ added custominfo command (check docu for details)  
+ added permissions PERMISSION_b_client_custom_info_view
+ added permidgetbyname command (check docu for details)
+ added b_virtualserver_permission_reset
+ added command permreset (check docu for details)
! added b_permission_modify_power_ignore permission, allows to 
  add/delete permissions without having the needed grant values
! added command line parameter dblogkeepdays (default 90)
  defines how many days to keep database log entries
  (triggered on every start and while running every day)
! added command line parameter dbclientkeepdays (default 30)
  removes all clients which had not connected the x days and dont
  got an servergroup assigned
  (triggered on every start and while running every day)

Linux users take note:
The server now must be started with LD_LIBRARY_PATH set to make sure the necessary
libraries are found, we now provide two scripts that do this. Use them to start the server:

• ts3server_minimal_runscript.sh - Behaves exactly like running ./ts3server_linux_{x86, amd64} did in previous releases
• ts3server_startscript.sh - This is a startscript that starts the server in the background, you can pass the parameters "start", "stop", "restart" and "status" to it. Note that since the server is started in the background you need to view the log files if any problems occure (since there is no output in your shell). Also if you have special command line parameters you wish to pass the server on startup, you need to edit the ts3server_startscript.sh the first not commented line COMMANDLINE_PARAMETERS="" is where you should edit

Have fun downloading

[R. Ludwig]

while cache builds up, http://ftp.4players.de/pub/hosted/ts3/releases/beta-17/

[stegmuellerm]

the server updates automatically, this sql statements are only needed to get access to the new permissions:

these are the command to update your database:

insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 2, 0, "b_client_custom_info_view", 1, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 2, 0, "i_needed_modify_power_client_custom_info_view", 100, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 3, 0, "b_client_custom_info_view", 1, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 3, 0, "i_needed_modify_power_client_custom_info_view", 75, 0, 0);

insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 2, 0, "b_permission_modify_power_ignore", 1, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 2, 0, "i_needed_modify_power_permission_modify_power_ignore", 100, 0, 0);

Attention:
From now, all Linux version must start with an startscript, this is included in the main folder of the teamspeak3 server installations

[KiLLers NL]

Does this startscript look at whether all ports are unbind before starting?

as that was one of my issues on previous version.

[Peter]

Does this startscript look at whether all ports are unbind before starting?

as that was one of my issues on previous version.

No it does not.

[Dennisen]

Can the new Command-Line parameters also be used in the .ini file?

[KiLLers NL]

No it does not.

ok thx, that i'll know i'll have to keep watching that, and having to set sleep to 10 perhaps.

[HarryRag]

Attention:
From now, all Linux version must start with an startscript, this is included in the main folder of the teamspeak3 server installations[/COLOR]

With the provides startscript or the versions we made ourself.
Starting our server with a script from the /etc/init.d/teamspeak3 as a service, can we just keep using that or is the provided start script a must?

[ScP]

insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 3, 0, "b_permission_modify_power_ignore", 1, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 3, 0, "i_needed_modify_power_permission_modify_power_ign ore", 75, 0, 0);

Actually, it would be REALLY BAD to grant these permissions to a server administrator...

[SmokinShark]

Works fine! Nice work!

[MoXNoX]

the server updates automatically, this sql statements are only needed to get access to the new permissions:

these are the command to update your database:

insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 2, 0, "b_client_custom_info_view", 1, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 2, 0, "i_needed_modify_power_client_custom_info_view", 100, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 3, 0, "b_client_custom_info_view", 1, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 3, 0, "i_needed_modify_power_client_custom_info_view", 75, 0, 0);

insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 2, 0, "b_permission_modify_power_ignore", 1, 0, 0);
insert into perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip) values (0, 2, 0, "i_needed_modify_power_permission_modify_power_ignore", 100, 0, 0);

Thanks stegmuellerm for the info! But, I'll try once more to pry out some response from the Teamspeak developers regarding the server upgrade. Can you guys confirm the above database changes? Thousands of server installations can become broken if server admins follow wrong instructions, leading to many frustrated people. Why is it so hard to provide exact database query commands at least with the release notes, if you can't automate the process? This is getting ridiculous...

[Gryphon]

Thousands of server installations can become broken if server admins follow wrong instructions, leading to many frustrated people. Why is it so hard to provide exact database query commands at least with the release notes, if you can't automate the process? This is getting ridiculous...

TS3 is still in beta, you signed up for such frustrations, it is not meant for anyone so dependent on it.

[MoXNoX]

TS3 is still in beta, you signed up for such frustrations, it is not meant for anyone so dependent on it.

Yeah, fair enough, I can live with the manual database upgrade for the early stage of the open beta, I guess it will be automated at some point. But what prevents TS devs for at least confirming that the SQL queries posted by forum members are right or not, if the devs don't bother to post them themselves? It's such a small ammount of work, measured in a minute or two for instant customer satisfaction

[paul26]

hello,

since we have update our server from beta 16 to beta 17 we have a big problem


i think 1 hour there is no problem and than i think for 5 minutes the ping of alle Users are up to 700+ an then all pings were normal and this is every hour.

So can someone tell me what can i do?!

Alle ressources from the root Server are brilliant and no Alerts were found in the log

gruß
sry for my bad englisch

[azzy101]

updated from 16-17 linux32 smoothly