TeamSpeak 3 Server 3.0.0-beta17 Available

[SmokinShark]

Works fine! Nice work!

[SeToY]

But the serveradmin password is now gone - you don't see it in the logs like the token now. :<

What about this problem?
I can't add new servers :<

[mm-de]

And how i can update the Server-Software without reinstalling?

[kevin]

Problem Update:

It runs as root, but i want to know the permissions i have to give my user account for running it as a user on a server?

[abishai]

I am a new to server updates as I started with beta16. Can some one explain a purpose of sql inserts on the first page ?
They add default permissions or these queries can be necessary to normal server operation ?
Can I add them from a client/console manually ?

[Polarhannes]

Problem Update:

It runs as root, but i want to know the permissions i have to give my user account for running it as a user on a server?

chown -R useritshouldrunas:useritshouldrunas /path/to/teamspeak3
chmod -R 770 /path/to/teamspeak3
chmod ug+sx /path/to/teamspeak3/ts3server_*

edit "useritshouldrunas" to fit your user and group, change /path/to/teamspeak3 to your ts3 path
done

Now even if you run it as root, it will be started as "useritshouldrunas". More information about this: http://de.wikipedia.org/wiki/Setuid

[BlueRey]

Well done!

[VPope]

So i have updated and droped my database wanting to rebuild it , but now when i run
./ts3server_linux_amd64 dbplugin=ts3db_mysql dbsqlcreatepath=create_mysql/

i get the message

2010-02-02 23:37:26.875541|INFO |DatabaseQuery | | Please make sure you use the supplied ts3server_runscript.sh to run the server, or set LD_LIBRARY_PATH yourself
2010-02-02 23:37:26.875665|CRITICAL|DatabaseQuery | | unable to load database plugin library "libts3db_mysql.so", halting!

and the database is not being built.

Is there a new syntax to start a server for the first time and have it build the indexes ?

[kevin]

chown -R useritshouldrunas:useritshouldrunas /path/to/teamspeak3
chmod -R 770 /path/to/teamspeak3
chmod ug+sx /path/to/teamspeak3/ts3server_*

edit "useritshouldrunas" to fit your user and group, change /path/to/teamspeak3 to your ts3 path
done

Now even if you run it as root, it will be started as "useritshouldrunas". More information about this: http://de.wikipedia.org/wiki/Setuid

Works! Thanks

[flightwatch]

the mimiman script works

but the other not.
-bash: ./ts3server_startscript.sh: /bin/bash^M: bad interpreter: No such file or directory

strange

[TexasTeamspeak]

Maybe its just me, after upgrading from beta16 > 17 win x64. Quite a few server group permissions were incorrectly enabled on all servers in the instance after this upgrade.

For example: beta16: b_modify_virtualserver_maxclients was not granted on any server then after the upgrade to beta17 every ServerAdmin group on every server had this permission.

[Dennisen]

Noone knows if the new startparameters can be used in the server.ini, too?

[x.wolverine.x]

Noone knows if the new startparameters can be used in the server.ini, too?

What do you mean with new startparameters in the ini?

Maybe you mean how to load the ini file with the new ts3server_startscript.sh?

If yes, then edit the COMMANDLINE_PARAMETERS="" on top of the the ts3server_startscript.sh like this:
COMMANDLINE_PARAMETERS="inifile=ts3server.ini"

[jayw654]

Any chance that they'll add an option "ban from channel" soon? To further explain this feature would ban a user from the channel but not the server, this allows the user that was banned from a specfic channel to enter a different one. Why do i see it as a need? Well when opening the server to the public some people are simply vindictive and malicious and simply like to cause problems and with the current methods are a bit harsh. As is a guest user can simply walk in and create a channel and become chan admin then wait for an unsuspecting user to walk to simply up and ban the person entering the channel for no reason just because the lousy admin thinks its "fun". Yes, this have see this happen on other chats systems often but it doesn't matter that it happens because on those system the admin/moderator only has the power to ban the person only from that channel/room. Well their you have a complete explanation of the reason for the request for feature "ban from channel". Also, I know that the server admin can simply ban the person being vindictive and malicious but the problem is that by the time i would find out many people would have been needleesly been banned from the server.

[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...