Here you can leave your feedback and discuss about server 3.6.x release.
The full details about that version can be found in our release thread.
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
Here you can leave your feedback and discuss about server 3.6.x release.
The full details about that version can be found in our release thread.
Last edited by dante696; January 30th, 2019 at 08:50 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?
Hello Dear Staff,
Please check ticket: #ZAJ-398-52012
Reported already 2 problems, one critical and one with low priority. that's all what i can share here.
Last edited by dante696; January 24th, 2019 at 08:04 PM. Reason: merged, see post 9
Is it an exploit to get some privileges?
Hmm did read your pm and replied a minute ago.
edit
Saw your second post in ticket. This is known and on todo for next bigger update.
Would have delayed the release of 3.6.0
Hint: Doing ticket and here in forum is a bit contra productive and confusing for everyone else.
@ florian
It's not about an exploit.
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?
I always preffer public posts as long no private data are involved.
The advantage is that other users with same problem get the answer or can give us more details.
I / We will check that and report back.
@ flo
It's about dropping connections. Not about an exploit or security breach.
I move the posts into the release thread. Since the bug wasn't posted here.
Last edited by dante696; January 24th, 2019 at 08:14 PM.
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?
This new update is shit.
I used querybots on my server, before update it was ok, no bugs etc.
Then when I updated and my querybots had join to server executed something like 5 commands and all server crushed...
I have no idea what's going on. I can't fix it.
I think it can be related to new query update, but why all server crushes?
Can you give me some advice about server query bots.
Because when I start query bots server is running something like 10 senconds more and crushes.
And I can't start server for +/- 10 minutes.
I have looked into logs and there is nothing...
I just made update in my hosting, same thing discovered already reported in ticket, to the 3.6.0 server bot is connected into console RAW or SSH does not matter, after some time rapidly and completely random your server drop all connections, clients can not connect again to the server also you can connect to the console Query but it is not respond even you can not execute ctrl +c to exit terminal, then you have to kill process and restart again in new shell, what is interesting process in Linux during drop all connections is still running not logs nothing else but otherwise can you add to the startup ./ts3server_startscript.sh additional command: logquerycommands=1 and see what bot did as last command before drop all connections? remember this command is good only for debug your logs will increase immediately with size.
There are currently 1 users browsing this thread. (0 members and 1 guests)