what can we do against that?....my teamspeak crashes like 500 times aday.
-= 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 Addict =-
I had 1 crash with Server 3.7.0 within 24h after i did the update.
But since then the server runs fine without problems or crashes.
-= TeamSpeak User =-
Anyone else is seeing a lot of CPU uses, even if theres only 1 person connected?
-= TeamSpeak User =-
For me, the fact that Speex was dropped is pretty sad, since I was using Speex Ultra-Wideband for every room on my server with max quality settings.
Plus I still feel that Speex Ultra-Wideband on quality 10 sounds way better than Opus Voice on quality 10. I liked the fact TS is also supporting Speex unlike Discord, which uses only Opus. But hey, at least for now I can keep the codec on rooms where it was before...
-= TeamSpeak User =-
Greetings, 3 days ago i updated from 3.6.1 to 3.7.0.
Since ive done that, connecting to the server takes more time (arround 6 seconds). PPL connecting via domainname. The DNS has a srv record for this, we dont use TSDNS. I also tested to switch back to previous version, cause i save backups for me, from the install files. This seems to work normal without any problems. Almost insteant connect (arround 1 sec).
What is the Problem and how to solve it?
Greetings Arikarion
-= TeamSpeak User =-
Are you deaf? It is not even comparable how huge of a difference there is. Opus is the superior codec.Originally Posted by MagicD3VIL
-= 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.
-= TeamSpeak Addict =-
Maybe Teamspeak can give us the option to set a codec quality beyond 10.
Maybe to 12 or 15 for people who want an extremely high quality.
Why was the latency setting dropped with opus?
Like Johnny Wiseau once said "we did nat".
The setting is still included and working as before.
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 =-
I Just discovered two new glitches on ts 3.7
The first is a member can open the mic to himself when the room has higher talk power without a permissions
the second is the server went down because of the script that is made by removed
Last edited by dante696; March 27th, 2019 at 09:36 PM.
Yeah we made a mistake in last release and an old behavior returned.
We will release version 3.7.1 tomorrow to fix and seal 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 Fanatic =-
Can we expect this part of the changelog for the current version to become a requirement with 3.7.1? Or, is that plan being pushed to versions >= 3.8.0?
Code:Important: Future releases of the Linux server will require glibc 2.17 or newer. Any older version will not be supported anymore.
Last edited by Screech; March 28th, 2019 at 01:39 PM. Reason: because -> become
No. We won't announce this twice.
This is a hotfix and will not be part of the log for 3.7.1.
Version 3.8.0 will require glibc 2.17 or newer.
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?
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
