TeamSpeak 3 Server 3.0.0 preview available

[R. Ludwig]

Note: This is a preview-release, We do NOT advise its use in production environments, please only use it to (a) preview and prepare for upcoming changes and (b) test and report flaws

Greetings,

we are happy to announce the preview release of a new server build with version 3.0.0.

Complete list of changes:

=== Server Release 3.0.0 01 Aug 2011
+ serversnapshotdeploy can deploy into a new virtualserver now, to archive this do a "use 0"
  just before the command
+ clients table got a new field "client_lastip" where we store last ip used by the client
- clientdbinfo, clientdblist, clientdbfind does show client_lastip
- fixed clientdblist count parameter returned always 1
- fixed issue where server kept status virtual_online while using logout command
- fixed problem where a channel you could not subscribe was not automatically
  unsubscribed when you left it
- fixed issue where VIRTUALSERVER_ASK_FOR_PRIVILEGEKEY && VIRTUALSERVER_AUTOGENERATED_PRIVILEGEKEY
  where exported/imported through a snapshot
- fixed issues with channel permission wont take values from clientchannel permissions
- fixed multiple complains by one user possibility if autoban count is set to two
- fixed strange serverquery password behavior
- improved client traffic reset performance
- improved database performance

http://ftp.4players.de/pub/hosted/ts...leases/server/

This thread is for reporting issues with this version - no feature requests or general problems. Posts of that kind will be removed. For some features you need a new client which is not available yet (or use beta channel).

[R. Ludwig]

there are currently two known bugs which we are hunting for:

1: after virtualserver restart some channels cant be loaded again and the log file contains an error like:

ChanClients() unable to load channel(ID: 207) from db, skipping. Error was: duplicate orderID
ChanClients() unable to load following channels, because of missing zero channelOrderID

2: a client is added multiple times to the same servergroup (completly harmless) which can result in one of this errors:

cldbid: 2223, double assigned for sgid: 223, ignoring!
client pruning: memory delete failed for cldbid: 3434, error: database empty result set

any HOWTO would be very welcome!

[imRa-lm]

1] i wrote a howto a while ago [the link is placed at the bottom of '1]']. ya only have to replace the channel ids w/ the one from your own log n edit the order id for them. for everyone who like to use the solution:

- stop your ts3 server [recommended]
- make a backup from your db
- read the error log n posts carefully [ya can skip the other issues]. don't jump to the last post n edit the channels if ya don't understand how the system works

how to fix the issue

2.1] cldbid: 2223, double assigned for sgid: 223, ignoring!

replace the numbers w/ the numbers from your error-log.

]SELECT * FROM `group_server_to_client` WHERE `group_id` = 223 AND `id2` = 2223;

if ya receive more than one row, then delete every row except one!

2.2] client pruning: memory delete failed for cldbid: 3434, error: database empty result set
for the second row i can't give any advice cuz i'm not sure where the error is located. ya can walk through your db [clients, group_channel_to_client, group_server_to_client, perm_client] n search for the client id?

[dante696]

Thank you for your help, but we need a normal How to reproduce. This tells us how to fix the problem, when it happend.

[hunterpl]

Hello im currently using rc-2 server and sometimes show me message that and server stop crash...

2011-07-18 16:39:45.810006|CRITICAL|PermissionMgr | 1| channelGroupSetClient() unable to remove client from channelgroup cldbid: 6285, groupID: 90, channelID: 4353, inherited: 0, error: empty result set

but group exist channel exist and user exist so tell me what the problem is ? why that happend ?

[imRa-lm]

i'm not sure if ya can repoduce the bug...your sql qrys are fine. it could be an ts->mysql transaction error which you can't handle w/ myisam.

also, i don't think it's a bug of the new release...it makes more sense that the error occurs days ago but they never restarted the server, so the error never appears inside the log. can sb confirm it? whoever have a backup from the db n ts could test it - in case they ran into the error after the update

[dante696]

This bug appears on sqlite and mysql and also happend on our servers. But we can't reproduce it since months.
This is the reason why we ask for help