SIGTERM after upgrade

[slackito]

I just updated my 3.9.0 ts3 server (which also made problems after upgrading, but was running fine now for a couple of months) to 3.10.0
I downloaded the .tar.bz2 and overwrote the extracted files with the existing ones just like the last time.
Made an system upgrade and rebooted.

Now my ts3 server stops after about 2 minutes, telling me it has been SIGTERM'd.
Its a VPS with 2GB memory, so i am pretty sure its not the OOM Killer.

I also deleted the /dev/shm/something... file, as this made problems a couple of times before.

The firewall is very restrictive, as this vps only hosts an apache with a static site and the ts3.

2019-11-13 08:38:45.794266|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.10.0 (2019-11-07 09:13:30)
2019-11-13 08:38:45.794914|INFO |ServerLibPriv | |SystemInformation: Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 Binary: 64bit
2019-11-13 08:38:45.794984|INFO |ServerLibPriv | |Using hardware aes
2019-11-13 08:38:45.796647|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
2019-11-13 08:38:45.796752|INFO |DatabaseQuery | |dbPlugin version: 3.11.1
2019-11-13 08:38:45.797492|INFO |DatabaseQuery | |checking database integrity (may take a while)
2019-11-13 08:38:45.867425|WARNING |Accounting | |Unable to open licensekey.dat, falling back to limited functionality
2019-11-13 08:38:45.867956|INFO |Accounting | |Licensing Information
2019-11-13 08:38:45.868022|INFO |Accounting | |licensed to : Anonymous
2019-11-13 08:38:45.868071|INFO |Accounting | |type : No License
2019-11-13 08:38:45.868207|INFO |Accounting | |starting date : Mon Jul 1 00:00:00 2019
2019-11-13 08:38:45.868232|INFO |Accounting | |ending date : Wed Jul 1 00:00:00 2020
2019-11-13 08:38:45.868248|INFO |Accounting | |max virtualservers: 1
2019-11-13 08:38:45.868262|INFO |Accounting | |max slots : 32
2019-11-13 08:38:45.963261|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-11-13 08:38:48.094196|INFO | | |Puzzle precompute time: 2152
2019-11-13 08:38:48.097422|INFO |FileManager | |listening on 0.0.0.0:30033, [::]:30033
2019-11-13 08:38:48.120705|INFO |Query | |listening for query on 0.0.0.0:10011, [::]:10011
2019-11-13 08:38:48.121701|INFO |Query | |listening for query ssh on 0.0.0.0:10022, [::]:10022
2019-11-13 08:38:48.122164|INFO |CIDRManager | |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128,
2019-11-13 08:40:16.001092|INFO |ServerMain | |Received signal SIGTERM, shutting down.

dmesg prints nothing relevant.

Anyone an idea what to do or how to get more debug information? I really dont want to strace that ...

edit: i found the problem. well, at least what is causing it but not why.
when i extracted the .tar.bz2, i did that as root. the ownership of the new files is - of course - root:root.
but my ts3 is running as user ts3server:ts3server. so i changed my /home/ts3server to ts3server:ts3server, and now everything runs fine again.

I dont know what exactly is going on behind the scenes, but i would print an error or at least a warning (if possible) if the .sh files, which are executed, are not owned by the user the ts3 server should run with.
Because, ts3 started fine, no error message in the logs except that evil SIGTERM all 2 minutes.