In this thread you can discuss or report or just ask everything about the TeamSpeak Server version 3.9.0.
The download and change log 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
In this thread you can discuss or report or just ask everything about the TeamSpeak Server version 3.9.0.
The download and change log can be found in our release thread.
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 =-
Nothing new about old free 512 slots license ?- Support for new license types (Gamer, Commercial, Sponsorship).
-= TeamSpeak Lover =-
Updated to 3.9.0 with no problem, supports NPL 512 slotsOriginally Posted by alex215
-= TeamSpeak User =-
Works also perfect for me now. Tested on Linux (Debian) x64 system. Also works smooth now on rasbian debian 9 with exagear deb 9. Thx much
-= TeamSpeak Lover =-
Is it normal that my sponsorship license continues to be called NPL in the server info?
Only when the license you mentioned isn't a sponsorship license.
Open your license with a editor and read what type it is.
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 =-
will upload the update here to dl.4players.de/ts/releases/
-= TeamSpeak Fanatic =-
That is no longer in use.
-= TeamSpeak Addict =-
Get the latest downloads here.
"dl.4players.de/ts/releases/" is not getting supported anymore.
-= TeamSpeak User =-
Great! Is it planned to also compile the server code for arm-architectures directly? That would make it unnecessary to use heavy tools like exagear for devices like Raspberry Pis. If so, what (approximate) time span are we talking about?
That is still unsupported.
He is using an emulator.
Last edited by dante696; June 30th, 2019 at 02:00 PM. Reason: meh tablet
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 =-
Maybe try reading that again and replying in a proper way.
-= TeamSpeak User =-
Hello guys,
today I updated our TS3 server with an NPO license from v3.5.1 to v3.9.0 on a Debian 8.11 environment with kernel:
Since then, it crashes randomly. I then started the instance within a screen-shell to see, what's the last message, as the ts3server-log-files do not contain anything.Code:3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux
What I could capture from the screen session is:
and from syslog:Code:ts3server has crashed. A crashdump has been generated at "/home/teamspeak3/crashdumps/ts3server_3_9_0_linux_amd64_b5bf-d140-f18d-9801.dmp" Segmentation fault
I also attached the crashdump here, maybe someone can help, what'S going on here?Code:Jul 1 17:45:18 de kernel: [20198151.559728] ts3server[17275]: segfault at 58 ip 00000000004c4954 sp 00007f78bd719e30 error 4 in ts3server[400000+81c000] Jul 1 19:37:29 de kernel: [20204882.918397] traps: ts3server[5255] general protection ip:4c494b sp:7f34ccaf2e30 error:0 in ts3server[400000+81c000] Jul 1 22:10:28 de kernel: [20214061.665253] traps: ts3server[17257] general protection ip:4c494b sp:7fdc80277e30 error:0 in ts3server[400000+81c000]
The previous version (3.5.1) worked fine.
If you might need anything else, let me know and I am happy to provide.
Thanks a lot for your help in advance!
Last edited by dante696; July 2nd, 2019 at 10:01 AM. Reason: merged
Thank you.
We can reproduce this crash and plan to release a hot fix today.
Visit this thread later this day to get the update.
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 this kernel is so damn old
I know its offtopic that theese are just CVE critical enough to get a livepatch:
https://patches.kernelcare.com/d2b2c...15/kpatch.html
you should update asap.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
