[Discussion] TeamSpeak Server 3.8.0 Beta

[Dorde]

Yes we announced that more RAM and also CPU may be needed for version 3.7.x but the usage shouldn't explode.

We need feedback for version 3.8.0. For older versions we have the feedback already.

I am using 3.8.0 beta-2 for 5 days now. There is no freeze, crash or something like that.

[dante696]

Did anyone here had such problem before?

[samurai-virgin]

Did anyone here had such problem before?

Hi, Dante.
I had one similar bug with 3.7.0
Instance took around 8-10GB RAM. (Recommendations about 200 servers/2000slots are followed)
I’ve forgot to send dump of process memory

[preterive]

Hello,
my server crashed a few days ago and now, wit the same descripted error.
Ubuntu 16.04 wit OpenVz, Kernel 2.6
i use Server 3.7.0, but now i will update to the 3.8.
The last Log, till it crashes: https://pastebin.com/0mqMVJXn
I have no new crashlog.
I used the Version 3.0.x on this Server too, a time ago.
I use the Sinusbot and the Ts3AudioBot https://github.com/Splamy/TS3AudioBot
i use the JTS3ServerMod from https://ts3bot.de/

i hope, this could help.

[I-MmmK-I]

Installed both beta versions on two different servers and there were no issues at all!

[Guraz]

Everything is fine since the update yesterday.

[Whittle]

[...]This delay also counts for the TeamSpeak 3 Client version 3.3.0.

Will a new version of the mobile app be released at the same time (i.e. one that supports signed badges)?

[florian2833z]

i_client_max_channel_subscriptions has no effect anymore

[XeruTec]

I just saw the delay post on your Beta Announcement.

a few days ago(i don't know the exactly day), ich had the problem that no one could connect via my/our main domain. They still could connect via the second domain, we use for such problems like this, and with the ip. I had to restart the server to fix that issue.

And we're running a ranksystem on our server which uses a serverquery. We have noticed it couldn't connect to the server because all our querys got deleted with 3.8.0-beta2.

Since 5 days, i noticed some users are dropping a few more times than before. Except that, there are nomore problems with our serverquerys or domain.

[dante696]

Will a new version of the mobile app be released at the same time (i.e. one that supports signed badges)?

A new version yes. At the same time can't promise this.

i_client_max_channel_subscriptions has no effect anymore

Looks fine here with values -1, 0, 5 or permission disabled. Got the error when my own subscription was at it's limit and tried to subscribe a new channel.

<08:22:41> insufficient client permissions (failed on i_client_max_channel_subscriptions)

They still could connect via the second domain, we use for such problems like this, and with the ip. I had to restart the server to fix that issue.

In the issue i did describe in the announcement nobody could connect any longer.
It did not matter from where they connect because the server process did hang and did not accept new connections.

We have noticed it couldn't connect to the server because all our querys got deleted with 3.8.0-beta2.

What do you mean with deleted?

[Dragon34]

Hello I may confirm a problem with domain names.


Several of my members could not connect with the domain name on my server (the domain could not be found) I also noticed this problem at planetteamspeak + pts for 48h.


Now remains to know if this is a server error or domain hosts

[dante696]

The server doesn't care about domains. He doesn't know which domains exist.
The client resolves a domain and if that worked before with same client then it is a network problem.

[florian2833z]

Looks fine here with values -1, 0, 5 or permission disabled. Got the error when my own subscription was at it's limit and tried to subscribe a new channel.

<08:22:41> insufficient client permissions (failed on i_client_max_channel_subscriptions)

Edit: nvm, i just found an error in my permission system that I've never noticed. I thought it was because of the update. Sorry.

[Pantoflarz]

Had the beta2 running on our setup since Tuesday.
No errors so far, no query crashes either.

Are you guys expecting this to be fixed with beta2 or are we very much still in the dark?

[dante696]

Tnx for the feedback.

We expect that but there are so many different configurations and possibilities out there that could still break.