[Discussion] TeamSpeak Server 3.8.0 Beta

[dante696]

This thread can be used to leave feedback or discuss about server 3.8.0 release.
The full details about that version can be found in our release thread.

[hunterpl]

Hello dante696

1 Error found. Does not work custom line parameter with commands, instance even do not start because not apply the command line parameters which are, the old script work but the new one doesn't:

BINARYNAME=ts3server
COMMANDLINE_PARAMETERS="dbplugin=ts3db_mariadb dbpluginparameter=ts3db_mariadb.ini default_voice_port=9987 voice_ip=178.217.186.148,2001:67c:2044:3123::2 filetransfer_ip=178.217.186.148,2001:67c:2044:3123 ::2 filetransfer_port=30033 query_ip=178.217.186.148,2001:67c:2044:3123::2 query_port=10011 query_protocols=ssh,raw query_ssh_ip=178.217.186.148,2001:67c:2044:3123::2 query_ssh_port=10022 dbconnections=10 logappend=1 query_buffer_mb=5 license_accepted=1 logquerycommands=0" #add any command line parameters you want to pass here
PID_FILE=ts3server.pid

[dante696]

Please put the parameters into the server.ini and use inifile=server.ini for the start.

or

Open the start script and in lines 107 & 116 replace ADDITIONAL_COMMANDLINE_PARAMETERS with COMMANDLINE_PARAMETERS

We will fix that for stable release.

[Dorde]

changelog correction: "ldd --version" instead of "ldd -version"

[hunterpl]

Please put the parameters into the server.ini and use inifile=server.ini for the start.

or

Open the start script and in lines 107 & 116 replace ADDITIONAL_COMMANDLINE_PARAMETERS with COMMANDLINE_PARAMETERS

We will fix that for stable release.

Yes now work fine, thanks.

[samurai-virgin]

Yes now work fine, thanks.

Hello!
For example: if we starting multiple instances from same directory with one binary file but with different ini config files with defined pid_file* parameters all is ok. But i have a question: how to stop started by this way instance ?

In ts3server_startscript.sh on stop command it is trying to stop process with pid from ts3server.pid. Is it will be improved for running multiple instances from one directory ?

*43 line was edited to for prevent replacing ini file pid_file parameter by "pid_file=$PID_FILE"

"./${BINARYNAME}" "${@}"

[boehseronkel]

Temporary passwords are now saved in the database and will load on server start.

Would be great if this would also be possible for temporary channels with an expiry date.

Also i hope, that the passwords are not going to be saved as plaintext in the DB.

[MTK0815]

the server starts correctly, but under "Version" it says allready "Version:3.7.1 on Windows"? My Fail?

[Screech]

Please put the parameters into the server.ini and use inifile=server.ini for the start.

or

Open the start script and in lines 107 & 116 replace ADDITIONAL_COMMANDLINE_PARAMETERS with COMMANDLINE_PARAMETERS

We will fix that for stable release.

or

Open the start script and in line 6 replace COMMANDLINE_PARAMETERS with ADDITIONAL_COMMANDLINE_PARAMETERS

[numma_cway]

The switch to view ldd version is --version, not -version.

[Chris]

The switch to view ldd version is --version, not -version.

See Post #4, it was already reported

[fqupl]

Seems the badges are gone since a while now. I can only see my own but not the badges from the other users. did anyone experience the same?

[Chris]

Seems the badges are gone since a while now. I can only see my own but not the badges from the other users. did anyone experience the same?

If that is a 3.8.0 server then yes that is expected. Badges are required to be signed with server 3.8.0, as such clients before 3.3.0 will not have badges.

[Saelyth]

My tests proved that I can send 8150 characters as text with a ServerQuery bot (will that be the new limit? such an odd number, I'd expect something like 10000), but my Teamspeak client (3.2.5) still only let me 1024. The client needs to be patched I guess.

[Chris]

My tests proved that I can send 8150 characters as text with a ServerQuery bot (will that be the new limit? such an odd number, I'd expect something like 10000), but my Teamspeak client (3.2.5) still only let me 1024. The client needs to be patched I guess.

The limit is actually 8192 (which is not an odd/random number) single byte characters.
The client is still limited to 1024, since there was no update yet (other than the security fix in 3.2.5).