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
We are able to reproduce it and are working on a fix.
hunterpl's logs did help a lot!
Update (28th of Jan 2019)
Plan is to release server 3.6.1 tomorrow with 2 fixes.
One fix is for hanging server after Query interactions and the other one for wrong value for channel-client permissions.
Update 2 (29th of Jan 2019)
We could not release a server today.
Last edited by dante696; January 29th, 2019 at 04:51 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?
-= TeamSpeak Addict =-
Hello Dante696!Originally Posted by dante696
You are welcome in ticket i sent all logs + youtube videoclip with more additional debug logs. Additional i will report also problem with consumption ram after introduce a query buffor to the teamspeak 3 server from 3.1 version, i will explain it also in ticket.
This is not what i meant when i asked to report in only one system. Now only half information again is spread here.
For the Query bots where server dies we do not need anything else. We fixed that already but could not release the server yet.
Last edited by dante696; January 29th, 2019 at 11:57 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 =-
Guys, do somewhen max server query connections will increases ?
-= TeamSpeak User =-
Whats that? Can run the server on 3.6.0 and not 3.6.1 (release on 4players)
Downgrade to 3.5.1 and no more issues.Code:tail ts3server_2019-01-31__xxx_0.log [...] 2019-01-31 16:00:00.665616|INFO |Query | |creating QUERY_SSH_RSA_HOST_KEY file: ssh_host_rsa_key 2019-01-31 16:00:04.924099|CRITICAL|Query | |unable to create QUERY_SSH_RSA_HOST_KEY ('ssh_host_rsa_key')
Works fine here and there was no change for that since version 3.3.0
The only change in server 3.6.x was that SSH is activated by default and that one needs the rsa key.
When you start server 3.5.1 with following parameters then the result should be the same.
Make sure that your executing user owns permissions to write into the server directory.Code:query_protocols=ssh query_ssh_rsa_host_key=ssh_host_rsa_key or use attached ini file and parameter inifile=ts3server_ssh.ini
As temporary fix (not the soloution!) you can start the server with parameter query_protocols=raw
Be warned raw might be removed in future.
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 =-
Issue fixed Dante.
Mistakenly run my updatescript as root which resulted in the server shortly starting as root before my service took over and run it with the appropiate user. Thus the rsa_key_file got created as root and the usual user running ts3server coudn't access it.
-= TeamSpeak Lover =-
Is 3.6.1 going to be released on the main website download page? It's been a few days and still shows 3.6.0 for me.
-= TeamSpeak Addict =-
https://files.teamspeak-services.com.../server/3.6.1/
-= TeamSpeak Lover =-
Dear Tim,
why you forgot update your current server version here?
https://www.teamspeak.com/versions/server.json
Last edited by dante696; February 4th, 2019 at 08:39 AM. Reason: merged
-= TeamSpeak Lover =-
I asked yesterday but have yet to receive a response
-= TeamSpeak Lover =-
with 3.6.1 every day connection was lost with server, no user could enter, but TS was not broken, I only saw this in the rare and different logs for me:
2019-02-01 18:46:24.385288|INFO |PktHandler |1 |Cleaning up connection because of 12 resends of COMMAND packet
2019-02-01 18:46:24.385359|INFO |PktHandler |1 |Dropping client 96 because of resend timeout
I went back to 3.6.0 and nothing happened again, as in the past without any problem
-= TeamSpeak Addict =-
Please don't tell me someone needs to update this file by hand whenever there is a new release.
-= TeamSpeak User =-
Es gibt ja denn Rang "Server Query" denn man sich über YatQa geben kann, oder besser gesagt konnte. Denn wenn ich es jetzt versuche mir Server Query zu geben kommt eine Fehlermeldung die Besagt das Teamspeak in der bisher neusten Version (3.6.1) etwas entfernt hat was zu dieser Fehlermeldung kommt und kein Probmelm von YatQa ist.
Jetzt zu meiner Frage(n):
Ist das so gewollt oder wird sich um das Problem gekümmert?
Ist das wirklich ein Problem von Teamsepeak?
P.S.: tut mir leid falls diese Frage schonmal gestellt wurde. :)
Last edited by dante696; February 18th, 2019 at 03:52 PM. Reason: merged
Es ist kein Problem und es war nie eins.
Wir wollten nie, dass User sich Query Gruppen zuweisen. Für Clients gibt es die Server Gruppen.
Mit Server 3.6.1 handeln wir nun.
Kein ProblemP.S.: tut mir leid falls diese Frage schonmal gestellt wurde.
Last edited by dante696; February 18th, 2019 at 04:58 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?
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
