This thread can be used to leave feedback or discuss about server 3.7.0 release.
The full details about that version can be found in our release thread.
This thread can be used to leave feedback or discuss about server 3.7.0 release.
The full details about that version can be found in our release thread.
Last edited by dante696; March 19th, 2019 at 02:55 PM. Reason: updated url
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?
-= TeamSpeak User =-
Funkioniert alles wunderbar / working all fine.
Gruß / greeting
Killer0561 (Sascha)
-= TeamSpeak Fanatic =-
If I'm on holiday and don't test a TeamSpeak server...
- "instanceinfo" returns permission version 22. This is incorrect. 3.6.0 had version 22 already, but 3.7.0 is different. However, either 3.3.0 was version 21, so 3.5.0 must have been either 21 or 22 while having another set of permissions... Or do you not count permission sets with removed permissions?
- Changes in the permissions are incomplete in the changelog. The codec speex and CELT permissions were removed: b_channel_create_modify_with_codec_speex8, b_channel_create_modify_with_codec_speex16, b_channel_create_modify_with_codec_speex32, b_channel_create_modify_with_codec_celtmono48
- i_channel_create_modify_with_codec_latency_factor_ min refers to a setting that is not available for opus channels. So this permission exists, even though no compatible codec does.
-= TeamSpeak Lover =-
use debian 7, vps that takes by default, has EGLIBC 2.13-38 + deb7u12) I find little info or error to update, can you help?
@numma
- We haven't touched the permission version. But we may have should done that.
Update: We have 2 update mechanisms and this time we did use another one as before. That one does not raise the permission version. Next time we add, remove or rename permissions we will raise the version.
But please do not use the permission version for anything. That one is only for internal use.
- We summed it up with the first removed entry. For future we will add such details again.
Guess both points are helpful for tool devs.
- not sure if that is the case. But as long the codecs still can be used on old channels we better leave that one permission in the server.
@skorpe
What are you asking here? I don't get it.
The server should run as before.
The next one requires you to ensure that glibc 2.17 or newer is available.
I can tell that eglibc was discontinued in 2014 and debian 8 should have at least glibc 2.19.
But please use the internet search function for more details.
Last edited by dante696; March 20th, 2019 at 09:32 AM.
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?
-= TeamSpeak Lover =-
I was afraid, note that debian 7 only has stable up to 2.13, for superior it is necessary to update debian 8 min, all update of repositories of debian 7 are obseletas, maybe it will be a requirement to take into account minimum debian 8
2.13 is newer than the required 2.12.
So 3.7.0 should start like 3.6.1 did.
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?
-= TeamSpeak Fanatic =-
I think that having the permission version is incredibly useful for tool programmers. YaTQA could automatically download the permissions from the server if an unknown permission version is used.Originally Posted by dante696
Or YaTQA could use the server version (and and build date if needed) to archive that.
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?
-= TeamSpeak Lover =-
Well debian 7 is unspported since may 2018 any running such system almost a year later it should be consinderd compromised at this point.
-= TeamSpeak User =-
Hello! I have a serious problem.
Last Night, all servers in Romania with the version under 3.7.0 were dropped, including mine, with error:
LTC_ARGCHK 'in != NULL' failure on line 100 of file ../../../../s/deps/ts_tomcrypt/src/pk/ecc/ecc_import.c
ts3server has crashed. A crashdump has been generated at "/opt/sell/teamspeak20870/crashdumps/ts3server_3_6_1_linux_amd64_b086-982b-2cd0-551c.dmp"
What can we do? I understand it is a exploit done with the reason of flooding the teamspeak servers to move us to discord.
Last edited by dante696; March 24th, 2019 at 03:49 PM. Reason: merged
-= TeamSpeak User =-
what can we do against that?....my teamspeak crashes like 500 times aday.
Last edited by dante696; March 24th, 2019 at 03:48 PM. Reason: merged
For those who report a crash on server 3.7.0
1. Update to the stable version of 3.7.0
https://www.teamspeak.com/en/downloads/#server
2. Please add server log 0 if that version still does crash.
@Alex
Reporting bugs from old versions are useless. That bug from version 3.6.1 was fixed in 3.7.0.
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?
-= TeamSpeak User =-
You are semi-correct.
The servers do not crash, but all clients are dropped with the log showing stuff like this:
The server doesn't actually crash. The 0 log contains this in the end:Code:2019-03-24 15:26:06.958217|INFO |VirtualServerBase|1 |client disconnected 'ddddddddd'(id:3299) reason 'reasonmsg=connection lost' 2019-03-24 15:26:07.459633|INFO |PktHandler |1 |Dropping client 93 because of ping timeout 19 0 0 2019-03-24 15:26:07.459723|INFO |VirtualServerBase|1 |client disconnected 'aMepukaHo'(id:3869) reason 'reasonmsg=connection lost' 2019-03-24 15:26:14.169691|INFO |PktHandler |1 |Cleaning up connection because of 15 resends of COMMAND packet 2019-03-24 15:26:14.169767|INFO |PktHandler |1 |Dropping client 39 because of resend timeout
Server version is 3.7.0.Code:2019-03-24 14:46:27.420931|INFO |Query | |listening for query on xx.xx.xx.xx:10011 2019-03-24 14:46:27.421570|INFO |Query | |listening for query ssh on 0.0.0.0:10022, [::]:10022 2019-03-24 14:46:27.421606|INFO |Query | |creating QUERY_SSH_RSA_HOST_KEY file: ssh_host_rsa_key 2019-03-24 14:46:30.122344|INFO |CIDRManager | |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128,
This started happening since yesterday. Server was on 3.5.1 back then, but is now on 3.7.0 and it's still happening.
-= TeamSpeak User =-
I can give you this truth. Since I upgraded the server, I did this too. All connections were dropped by the server, but the server ran further. Before that, 3.6-1 was never the same.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
