Broken TS3 Server Start after Update

TeamSpeak Server
1

It doesn’t matter if I use a normal linux setup or the docker version becuase you guys failed in learning how to write “DB CREATE” Blocks correctly.

1st: NEVER EVER MISS !!! CREATE TABLE IF NOT EXISTS !!! because now my Instance is stuck trying to create a table which already exists.

If you have changed anything in a table then do !!! ALTER TABLE !!! in an update scipt, please.
Not I must celan up your dirty pice of ■■■■ like every time and this is frustrating!

Please, please learn how to code SQL correctly, please!

And also change the old dbPlugins Version from 2 to 3, cause it’s outdated …

2021-10-15 21:18:31.265061|INFO    |ServerLibPriv |   |TeamSpeak 3 Server 3.13.6 (2021-06-09 10:22:37)

2021-10-15 21:18:31.265168|INFO    |ServerLibPriv |   |SystemInformation: Linux 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 Binary: 64bit

2021-10-15 21:18:31.265203|INFO    |ServerLibPriv |   |Using hardware aes

2021-10-15 21:18:31.265448|INFO    |DatabaseQuery |   |dbPlugin name:    MariaDB plugin, version 3, (c)TeamSpeak Systems GmbH

2021-10-15 21:18:31.265489|INFO    |DatabaseQuery |   |dbPlugin version: 2

2021-10-15 21:18:31.269990|ERROR   |DatabaseQuery |   |db_exec() CREATE TABLE channel_properties (  server_id integer unsigned,  id     error: Table 'channel_properties' already exists

2021-10-15 21:18:31.270052|CRITICAL|SQL           |   |db_CreateTables() unable to create tables

Now I must take a look into this and hardcode this ■■■■ in so please check your scripts, thanks.

And NO!!! I am not going to downgrade MariaDB because you guys can not update/upgrade/code your things correctly, so it’s your fault!

2

Please take a look into this Thread: Server with MariaDB Plugin can't create tables

3

This doesn’t helps and not solves the problem.

Containers where stoped and removed as they never existed before (only serverfiles and db files where still left to be remounted and loaded again) and then I pulled the new images for TS 3 and for MariaDB and still running in this error.

Sorry, but who ever uses SQL has to use “IF NOT EXISTS” in any create statement (table or database, don’t care about this part).

I don’t care if it works on Windows, LXC, LVM or what ever system as is isn’t nearly the same configuration as my system has and this is Debian 11 with docker, gitlab in docker + gitlab-runner (used from buster as there is no bullseye package yet but it runs smooth) and then the corresponding docker-compose.yml which has never had so many problems.

Only after this pull things are broken and this can’t be!