Same here can not reproduce on Linux & FreeBSD.
I think you just started server different then before or a service does kill the server.
Merged to thread where your other thread got merged into already.
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
Same here can not reproduce on Linux & FreeBSD.
I think you just started server different then before or a service does kill the server.
Merged to thread where your other thread got merged into already.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
There is actually one difference. I started teamspeak with crontab:
If you wish to reproduce the problem, add to crontab something like this (not exactly reboot, because not all servers can be rebooted adhoc)
@reboot /home_path_to_teamspeak_server/./ts3server_startscript.sh start
Then, after login and logout, server should shutdown.
Worked for me on 3.9.1 and 3.10.1.
Created that crontab and connected via SSH to machine and/or to ServerQuery SSH and closed the connections.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Last edited by bialy; November 21st, 2019 at 04:26 PM. Reason: update
I believe you already but i can not reproduce it (even with your videos).
Maybe log shows a reason? Maybe you see a SIGTERM there?
Maybe your .logout file contains commands to kill user process. Or your host has such script running doing this.
Last edited by dante696; November 19th, 2019 at 11:16 AM.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
My .bash_logout file contains
Nothing like "kill all"if [ "$SHLVL" = 1 ]; then
[ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
fi
I'm using ubuntu 18.04.
It's really weird.
And it's not only one server provider. I have different servers in different data centers.
And ts server log0 says?
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Nothing in log really...
Looks like server is killed without ability to write to the log.
Maby some "new" feature in newest ubuntu update? I'm really curious what happened...
latest log0 - http://scr.ovh/i/191121010261e.jpg
In your videos it got a shutdown command and did not get killed. So something shut be logged.
You may try all of this without any crontab for the TS server process.
Sorry have no idea why you have such issue.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Don't worry. I know how to deal with it.
It happend very rarely that ts3 goes offline or server need to be rebooted. That's why I have added it to the crontab.
Unfortunately, no. I just workaround with crontab but I did not find how to really fix this.![]()
There are currently 1 users browsing this thread. (0 members and 1 guests)