Please note the binary has changed to ts3server.exe. The dump is for ts3server_win64.exe which leads me to conclude you have started the wrong binary. If this is not the case please post the server...
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
Type: Posts; User: nwerensteijn; Keyword(s):
Please note the binary has changed to ts3server.exe. The dump is for ts3server_win64.exe which leads me to conclude you have started the wrong binary. If this is not the case please post the server...
Hi Thomas,
We are working on this issue. Currently the limit is 32 mb for all packages combined. This should soon be 32mb per package. Our apologies for the inconvenience in the mean time.
you can test 3.0.13.6 beta 1 to see if this problem is resolved: http://dl.4players.de/ts/releases/pre_releases/server/3.0.13.6-Beta-1/
This dump was not what I expected. It shows a server idling normally. I have some questions:
Was this dump created when the ts3server was not accepting new clients any more?
When the ts3server...
Note that we try to do all dns resolves at the same time. If we waited for each dns response, then try to see if we can contact a ts3server/tsnds server there, it would cause a massive delay. In the...
I (think I) fixed the problem for you on github hunterpl. Please have discussions about this code on github.
The reason why we decided this, is because it benefits a larger group of users. Not searching for tsnds on 2 or 3 A/AAAA records (in addition to SRV) helps make the client connect quicker to servers....
We are not removing TSDNS. But we are removing one of the ways the client can find it. TSDNS is found through either A dns records, or a _tsdns SRV record. We are deprecating the A record method.
...
Then do not use them, use a better registar :)
Hi Florain,
We want to remove non srv tsdns lookups, because they are slowing down the initial connection to ts3 servers. This is particularly noticeable on mobile clients.
The problem is that...
Sorry for the delay. The beta can be found here:
http://dl.4players.de/ts/releases/pre_releases/server/3.0.13.5-Beta-1/
Found the bug. It will be fixed in 3.0.13.5 release. We hope to release a beta on tuesday or wednesday
It means that in the past lavasoft web companion ad-ware was installed on your system. Most likely when some shareware program was installed.
This is a program that injects it self (thought code in...
Exactly right. The extra characters indicate that the query comes from a new client, which supports ipv6 and multiple ip's per hostname.
There are two reasons why we hash your password in the client (or on your browser) not our servers.
We do not receive your password, and so we do not know it. This is a major thing for us and...
We are working on a fix at this moment. We hope it will be available in beta tonight, and stable on friday
This crash seems to be caused by an exploit. It was fixed in 3.0.13.2
Everyone that is having this problem on a 64 bit linux system, please use the "gcore" program to create a core dump of the ts3server program while one or more of the virtual servers are unresponsive,...
Everyone that is having this problem on a 64 bit linux system, please use the "gcore" program to create a core dump of the ts3server program while one or more of the virtual servers are unresponsive,...
Everyone that is having this problem on a 64 bit linux system, please use the "gcore" program to create a core dump of the ts3server program while one or more of the virtual servers are unresponsive,...
what happens when you try to open http://files.teamspeak-services.com/updater-images/client/1461588969/update_win64.ini._lzma2_ in a browser?
We will add this in our next release. Maybe i can make a beta for this fix soon, but not for at least 2 weeks
I think you are experiencing the nagle algorithm https://en.wikipedia.org/wiki/Nagle's_algorithm and our write-write-read pattern. I guess we should enable tcp_nodelay on query to fix this.
What do you mean with "ServerQuery" ? do you mean that litteraly? or do you mean the unique id of a ServerQuery user?
yes.
The first script 'convert_mysql_to_mariadb.sql' converts an existing database. Basically the conversion is changing the currently used character set to 'utf8mb4'. Actually it has nothing to do...
How many times did it say that? There is a chance that you already had some bad characters in the client names for example. Did you use a special libmysqlclient before?
I would like to know if...
KIDINK^: Did you run the mariadb_fix_latin_utf8.sql script on a mysql client connected to your teamspeak database?
I am assuming you are using MySQL and that you ran the mariadb_fix_latin_utf8.sql script. Do/Did you?
can you tell me what what MySQL client you use and how it was compiled? (What I want to know is...
That was an oversight and will be fixed in the stable release. Thank you.
Eventually yes.
Can you check again. Hopefully your problems are now fixed
1. The speaker mask we use do not map 1 to 1 to wasapi or ds. If you look at public_definitions.h you will see that we use the non standard values:
#define SPEAKER_HEADPHONES_LEFT 0x10000000...
The answer all depends on how much time/money you want to spend and how generic your solution has to be.
The most generic I guess would be to do as you propose and use custom devices. This means...
It sounds like maybe your sound backends were not loaded. There should be a "soundbackends" folder in the same folder as your client binary. In that soundbackends forlder there should be one or more...
The problem is your libgcc_s is too old. I did not expect anyone to run into this problem but just in case we included this lib in redistributables. This is not your fault. We should have documented...