Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Page 1 of 2 12 LastLast
Results 1 to 15 of 69

Hybrid View

  1. #1
    Join Date
    September 2012
    Posts
    6,079

    TeamSpeak 3 Server 3.0.11.2 released

    Server version 3.0.11 is now available for download.

    The are some major changes in the MySQL database plugin, as well as some changes regarding query clients and permissions.
    We highly recommend making a backup of your existing database before testing this server, especially if you're using a MySQL database.

    Most notable changes in this upcoming server release are:
    • The MySQL plugin was removed in favor of Maria DB. At least MySQL 5.5.3 or MariaDB 5.5 are now required to run the server if you don't want to use the default SQLite database.
      You must convert your current MySQL database for Maria DB and utf8mb4 support. Please read the documentation for further details and instructions.
    • Guest ServerQuery clients' permissions can now be restricted with the negate flag. Many users had problems with query clients spamming chat messages and channels and this change allows to restrict this without affecting regular users. New server instances will restrict this by default, however for existing instances you'll have to modify the permissions accordingly if you wish to have this effect.
    • Query client logins are now bound to the server on which they were created and only receive that users' permissions on the virtual server they were created and will be treated as guest on other virtual servers.


    Please note that an SSE2 capable CPU is required to run the server on Windows.

    Full changelog below:
    Code:
    === Server Release 3.0.11.2 15 dec 2014
     - fixed possible deadlock in server query
     - fixed a mariadb/mysql db creation issue
     - fixed a mariadb/mysql performance issue
     - fixed a server query crash
    
    === Server Release 3.0.11.1 15 oct 2014
     - Small accounting fix
    
    === Server Release 3.0.11 30 sep 2014
     ! Starting this release, TS3 servers will not support the Mac OSX PowerPC architecture.
     ! Starting this release the Windows version of the server requires an SSE2 capable CPU.
     ! Starting 3.0.12 (next release), TS3 server won't support OSX 10.6 or lower.
     ! Starting this release, the MySQL database plugin has been replaced by a MariaDB plugin. Please
       read doc/update_mysql_to_mariadb.txt for instructions on how to update. Also note the default
       character set for the database is now 'utf8mb4', which means the server needs to be at least
       MySQL 5.5.3 or MariaDB 5.5 .
     ! When a new database is created, we will be using a few extra defaults for the Guest Server Query
       group. Permissions for existing databases will be left untouched.
       The new defaults for the Guest Server Query group should prevent the Server Query from being
       abused with spam. The extra permissions are:
       * b_channel_join_permanent = false, negate = true, skip = true
       * b_channel_join_semi_permanent = false, negate = true, skip = true
       * b_channel_join_temporary = false, negate = true, skip = true
       * b_channel_create_permanent = false, negate = true, skip = true
       * b_channel_create_semi_permanent = false, negate = true, skip = true
       * b_channel_create_temporary = false, negate = true, skip = true
       * b_client_server_textmessage_send = false, negate = true, skip = true
       * b_client_channel_textmessage_send = false, negate = true, skip = true
       * b_client_offline_textmessage_send = false, negate = true, skip = true
       * i_client_private_textmessage_power = -1, negate = true, skip = true
       * i_client_poke_power = -1, negate = true, skip = true
     ! If only 1 serveradmin is logged into the query, this serveradmin can select any server (use)
       regardless of the client limit.
     ! The "Wan IP" feature of the windows server has been removed as it does not work any more.
       If you want to know your wan ip address, use an existing free service like http://ipinfo.io
     + Updated ip2location database
     + Better checking and better error message for errors with query white/blacklists.
     - Fixed crash relating to invalid ip addresses on FreeBSD.
     - Fixed a possible crash during client connect.
     - Fixed channel event notifications stop working after a while.
     - Fixed query logins getting permissions on other virtual servers.
     - Fixed crash when deleting complaints.
     - Fixed issue where clients were not deleted from the database after dbclientkeepdays when
       connecting several TS3 servers to the same database with different dbclientkeepdays values.
     - The server instance no longer starts copies of virtual servers.
     - Guest ServerQuery user now always has default server query group, even while using a virtual
       server.
     - Instance server group permissions now honor the negate flag.
     - Temporary passwords and tokens(privilege keys) of a client are deleted when the client is deleted
       from the database.
     - Complaints of and about a client are deleted when the client is deleted from the database.
     - Fixed possible server hang with query connections.
     - ts3server_startscript.sh restart now works with parameters.
     - ts3server_startscript.sh does a better test for FreeBSD.
    Last edited by Chris; December 16th, 2014 at 07:23 AM. Reason: Updated for server 3.0.11.2

  2. #2
    Join Date
    September 2012
    Posts
    6,079
    To update an existing instance to use the new default restricted permissions for query guests use the following commands on the query interface:

    Code:
    login serveradmin PASSWORD
    servergroupautoaddperm sgtype=20 permsid=b_channel_join_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_join_semi_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_join_temporary permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_semi_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_temporary permvalue=0 permskip=1 permnegated=1|permsid=b_client_server_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=b_client_channel_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=b_client_offline_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=i_client_private_textmessage_power permvalue=-1 permskip=1 permnegated=1|permsid=i_client_poke_power permvalue=-1 permskip=1 permnegated=1
    Or run the following (Replace ANY_ACTIVE_PORT with a port of a running TS3 Server in your instance and PASSWORD with your actual password for the query):
    Code:
    login serveradmin PASSWORD
    use port=ANY_ACTIVE_PORT
    servergroupaddperm sgid=1 permsid=b_channel_join_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_join_semi_permanen t permvalue=0 permskip=1 permnegated=1|permsid=b_channel_join_temporary permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_semi_perman ent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_temporary permvalue=0 permskip=1 permnegated=1|permsid=b_client_server_textmessage_ send permvalue=0 permskip=1 permnegated=1|permsid=b_client_channel_textmessage _send permvalue=0 permskip=1 permnegated=1|permsid=b_client_offline_textmessage _send permvalue=0 permskip=1 permnegated=1|permsid=i_client_private_textmessage _power permvalue=-1 permskip=1 permnegated=1|permsid=i_client_poke_power permvalue=-1 permskip=1 permnegated=1
    Last edited by Chris; February 13th, 2017 at 02:00 PM.
    When sending PMs please make sure to include a reference link to the thread in question in the body of your message.

  3. #3
    Join Date
    December 2009
    Location
    UK
    Posts
    769
    Upgraded no problems using SQLite, but I foresee a lot of problems from MySQL users who don't bother reading changelogs (yes I know it's their fault if they crash & burn & don't have a backup)

  4. #4
    Join Date
    November 2010
    Location
    N/A
    Posts
    5
    Hey, I'm using MySQL (5.5.38) and tested the update on a local machine. After the first start of the instance all channels are deleted, except the lobby. Any ideas why this happens? I had to restore the "channels", "channel_properties" & "perm_channel" tables with my backup that I created before converting the tables - only then the server keeps the channels.

    Regards, Eggerd

  5. #5
    Join Date
    June 2008
    Posts
    18,513
    It's nothing, that happend during our tests.
    Did you read the update_mysql_to_mariadb.txt before updating?

    Any server logs availabale?
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  6. #6
    Join Date
    November 2010
    Location
    N/A
    Posts
    5
    Yes, I read the update_mysql_to_mariadb.txt and followed the steps on my local test machine.
    The server logs show the following:

    Code:
    2014-09-30 10:13:12.293175|ERROR   |ChanClients   |  1| ChanClients() unable to add channel(ID: 2), skipping. Error was: convert error
    2014-09-30 10:13:12.293175|ERROR   |ChanClients   |  1| ChanClients() unable to load channel(ID: 2) from db (missing channelOrderID: 1), deleting.
    2014-09-30 10:13:12.312176|ERROR   |ChanClients   |  1| ChanClients() unable to load channel(ID: 3) from db (missing channelOrderID: 2), deleting.
    2014-09-30 10:13:12.335178|ERROR   |ChanClients   |  1| ChanClients() unable to load channel(ID: 23) from db (missing channelOrderID: 3), deleting.
    2014-09-30 10:13:12.349178|ERROR   |ChanClients   |  1| ChanClients() unable to load channel(ID: 25) from db (missing channelOrderID: 23), deleting.
    2014-09-30 10:13:12.372180|ERROR   |ChanClients   |  1| ChanClients() invalid channel structure, not all channels could be loaded
    2014-09-30 10:13:12.372180|WARNING |ChanClients   |  1| failed to load: cID: 4 pcID: 2 deleting channel!
    2014-09-30 10:13:12.390181|WARNING |ChanClients   |  1| failed to load: cID: 5 pcID: 4 deleting channel!
    2014-09-30 10:13:12.409182|WARNING |ChanClients   |  1| failed to load: cID: 6 pcID: 4 deleting channel!
    2014-09-30 10:13:12.427183|WARNING |ChanClients   |  1| failed to load: cID: 7 pcID: 4 deleting channel!
    2014-09-30 10:13:12.446184|WARNING |ChanClients   |  1| failed to load: cID: 8 pcID: 4 deleting channel!
    2014-09-30 10:13:12.459185|WARNING |ChanClients   |  1| failed to load: cID: 9 pcID: 4 deleting channel!
    2014-09-30 10:13:12.482186|WARNING |ChanClients   |  1| failed to load: cID: 10 pcID: 4 deleting channel!
    2014-09-30 10:13:12.494187|WARNING |ChanClients   |  1| failed to load: cID: 11 pcID: 4 deleting channel!
    2014-09-30 10:13:12.507187|WARNING |ChanClients   |  1| failed to load: cID: 12 pcID: 4 deleting channel!
    2014-09-30 10:13:12.526189|WARNING |ChanClients   |  1| failed to load: cID: 13 pcID: 2 deleting channel!
    2014-09-30 10:13:12.544190|WARNING |ChanClients   |  1| failed to load: cID: 14 pcID: 4 deleting channel!
    2014-09-30 10:13:12.562191|WARNING |ChanClients   |  1| failed to load: cID: 15 pcID: 13 deleting channel!
    2014-09-30 10:13:12.580192|WARNING |ChanClients   |  1| failed to load: cID: 16 pcID: 13 deleting channel!
    2014-09-30 10:13:12.599193|WARNING |ChanClients   |  1| failed to load: cID: 17 pcID: 13 deleting channel!
    2014-09-30 10:13:12.617194|WARNING |ChanClients   |  1| failed to load: cID: 18 pcID: 2 deleting channel!
    2014-09-30 10:13:12.637195|WARNING |ChanClients   |  1| failed to load: cID: 19 pcID: 13 deleting channel!
    2014-09-30 10:13:12.662196|WARNING |ChanClients   |  1| failed to load: cID: 20 pcID: 18 deleting channel!
    2014-09-30 10:13:12.697198|WARNING |ChanClients   |  1| failed to load: cID: 21 pcID: 18 deleting channel!
    2014-09-30 10:13:12.738201|INFO    |VirtualServer |  1| listening on 0.0.0.0:9987

  7. #7
    Join Date
    May 2007
    Location
    Eastern NC
    Posts
    1,801
    Thank you. Update appears to be working fine on my servers using SQLite backend.

  8. #8
    Join Date
    March 2014
    Posts
    28
    Quote Originally Posted by Chris View Post
    To update an existing instance to use the new default restricted permissions for query guests use the following commands on the query interface:

    Code:
    login serveradmin PASSWORD
    use 0
    servergroupaddperm sgid=1 permsid=b_channel_join_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_join_semi_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_join_temporary permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_semi_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_temporary permvalue=0 permskip=1 permnegated=1|permsid=b_client_server_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=b_client_channel_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=b_client_offline_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=i_client_private_textmessage_power permvalue=0 permskip=1 permnegated=1|permsid=i_client_poke_power permvalue=-1 permskip=1 permnegated=1
    Doing this resulted in "error id=1024 msg=invalid\sserverID". However, if I "use 1" instead of "use 0" it works fine. Does this indicate a problem?

    (Linux x64; Debian 7; SQLite)

  9. #9
    Join Date
    September 2012
    Posts
    6,079
    Quote Originally Posted by Linnun View Post
    Doing this resulted in "error id=1024 msg=invalid\sserverID". However, if I "use 1" instead of "use 0" it works fine. Does this indicate a problem?

    (Linux x64; Debian 7; SQLite)
    No it doesn't, everything is fine.


    Quote Originally Posted by BaDaSS View Post
    The information in the ts3db_mariadb.ini is correct as far as username and password to the database.
    User and password maybe but not the connect information (e.g. socket or host/port)


    Quote Originally Posted by Tomi-Toma View Post
    There is something wrong with the temp. channel delete delay.
    The "bug" is also in the older versions.

    2 day´s are 172 800 sekunds but teamspeak shows that the channel is gonna be deleted in 24 hours.

    Name:  Unbenannt.PNG
Views: 1873
Size:  27.1 KB
    Can't reproduce. Possibly the channel existed before and was switched to Temporary. If the channel has been empty for 24 hours before you made those modifications (i.e. temporary and delete delay) it is correct in having a ~ 24 hour countdown.
    Also it looks like you've set the 2 day delay in the server options. Individual channels can still have their own delete delay specified in the channel edit dialog, which overrides the server default.
    Last edited by Chris; October 2nd, 2014 at 07:27 AM.
    When sending PMs please make sure to include a reference link to the thread in question in the body of your message.

  10. #10
    Join Date
    August 2014
    Posts
    4
    Why there was a downgrad of the SQLite Plugin.
    Server 3.0.10.3 use the Plugin Version 3.7.3 and Server 3.0.11 use 3.6.21 ?
    Platform is Linux

  11. #11
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266
    Quote Originally Posted by Tealc View Post
    Why there was a downgrad of the SQLite Plugin.
    Server 3.0.10.3 use the Plugin Version 3.7.3 and Server 3.0.11 use 3.6.21 ?
    Platform is Linux
    Good question. I didn't notice before... but you are right. The SQLite plugin was down graded.

  12. #12
    Join Date
    June 2008
    Location
    Krün, Germany
    Posts
    510
    Quote Originally Posted by Tealc View Post
    Why there was a downgrad of the SQLite Plugin.
    Server 3.0.10.3 use the Plugin Version 3.7.3 and Server 3.0.11 use 3.6.21 ?
    Platform is Linux
    That was unintentional. Should be upgraded again to the latest SQLite version with the next server release (not next hotfix, next real release). While somewhat unfortunate, there don't seem to be any issues with using the older SQLite plugin.

  13. #13
    Join Date
    October 2012
    Posts
    3
    Quote Originally Posted by Chris View Post
    To update an existing instance to use the new default restricted permissions for query guests use the following commands on the query interface:

    Code:
    login serveradmin PASSWORD
    use port=ANY_ACTIVE_PORT
    servergroupaddperm sgid=1 permsid=b_channel_join_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_join_semi_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_join_temporary permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_semi_permanent permvalue=0 permskip=1 permnegated=1|permsid=b_channel_create_temporary permvalue=0 permskip=1 permnegated=1|permsid=b_client_server_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=b_client_channel_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=b_client_offline_textmessage_send permvalue=0 permskip=1 permnegated=1|permsid=i_client_private_textmessage_power permvalue=0 permskip=1 permnegated=1|permsid=i_client_poke_power permvalue=-1 permskip=1 permnegated=1
    I thought the value of i_client_private_textmessage_power should be -1 and not 0, or am I wrong?

  14. #14
    Join Date
    September 2012
    Posts
    6,079
    Quote Originally Posted by elpronto View Post
    I thought the value of i_client_private_textmessage_power should be -1 and not 0, or am I wrong?
    you're right, it ought to be -1 or any other value below 0 really.
    When sending PMs please make sure to include a reference link to the thread in question in the body of your message.

  15. #15
    Join Date
    March 2014
    Posts
    28
    Since server version 3.0.11 I noticed a weird problem with serverwide packet losses and eventually tracked it down to be caused by server queries removing/adding clients to server groups.

    Let's say a server query client assigns 3 groups to a client:
    servergroupaddclient cldbid=100 sgid=50
    servergroupaddclient cldbid=100 sgid=51
    servergroupaddclient cldbid=100 sgid=52
    What happened BEFORE 3.0.11:
    The user instantly gets the 3 server groups assigned. That's it.

    What happens SINCE 3.0.11:
    The user gets the groups assigned one by one with an approximate delay of 1 second between each group. While the groups are still being assigned, the server has a huge packet loss (can be seen in server connection info; if someone is talking to you anywhere on the server, you'll also hear the packet loss).


    Usually this behavior is caused by a bot that uses server query to assign server groups to users. I have now manually tested this with a telnet client. I've tried it with a "normal" server query client and a Admin Server Query client, both cause the same problem.
    This has been tested with a big server that regularly has 150+ concurrent users and the server connection info shows an average packet loss of up to ~30%, so it's not just a connection issue by a certain user.

    The server is running on stable Debian x64 with sqlite.



    Can someone confirm/reproduce this problem? It's a pretty major issue, since we do rely on the bot managing some of the server groups.

    (edit: you may want to test this with more than 3 groups, or alternatively, more than one user each getting 3 groups)
    Last edited by Linnun; October 27th, 2014 at 11:05 PM.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 26
    Last Post: April 8th, 2014, 09:05 PM
  2. TeamSpeak 3 Server 3.0.10 released
    By Chris in forum Archive
    Replies: 8
    Last Post: October 24th, 2013, 09:43 AM
  3. TeamSpeak server 3.0.9 released
    By dante696 in forum Archive
    Replies: 39
    Last Post: September 22nd, 2013, 02:15 PM
  4. TeamSpeak server 3.0.8 released
    By Chris in forum Archive
    Replies: 14
    Last Post: September 12th, 2013, 08:48 AM
  5. TeamSpeak Server 3.0.7.2 released
    By Chris in forum Archive
    Replies: 10
    Last Post: May 20th, 2013, 04:32 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •