i’ve got a pretty annoying problem, i don’t understand.
Yesterday my server crashed out of whatever reason, i dont actually know why.
My Teamspeak is running on a vServer (Ubuntu Dist), i haven’t changed anything. It all worked fine earlier.
So, everytime i try to start my server with the “ts3server_startscript.sh” it says that the server started, but i can’t connect to it.
In the Logs it shows the “SIGTERM server stopped” error, thats usually output when the process is killed by the vServer itself.
But once i open YATQA it shows that the server is stopped, but when i start it in YATQA i’m able to connect to it.
I have no clue what’s actually happening.
I already updated the server software and i have a working license.
Hope you can help me!
Without any log or crashdump we also do not know why it crashed.
crashed really what happens? From your description i can not find anything crash related.
SIGTERM means the server got the request from something in your operation system to shutdown.
You have to find out what sends the SIGTERM command to the TS Server process.
Yeah, thats basically what i’m telling you. There is no real crash or error log, since the operating system is killing the process. But it’s not when im starting the server via YATQA ( query ).
2020-03-31 11:33:01.049096|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.12.0 (2020-03-18 11:53:17)
2020-03-31 11:33:01.049348|INFO |ServerLibPriv | |SystemInformation: Linux 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 Binary: 64bit
2020-03-31 11:33:01.049395|INFO |ServerLibPriv | |Using hardware aes
2020-03-31 11:33:01.050529|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, ©TeamSpeak Systems GmbH
2020-03-31 11:33:01.050573|INFO |DatabaseQuery | |dbPlugin version: 3.11.1
2020-03-31 11:33:01.050981|INFO |DatabaseQuery | |checking database integrity (may take a while)
2020-03-31 11:33:01.077424|INFO |Accounting | |Licensing Information
2020-03-31 11:33:01.077500|INFO |Accounting | |licensed to : *******
2020-03-31 11:33:01.077519|INFO |Accounting | |type : Activation License
2020-03-31 11:33:01.077547|INFO |Accounting | |starting date : ******
2020-03-31 11:33:01.077561|INFO |Accounting | |ending date : ******
2020-03-31 11:33:01.077572|INFO |Accounting | |max virtualservers: 2
2020-03-31 11:33:01.077583|INFO |Accounting | |max slots : 128
2020-03-31 11:33:02.019491|INFO | | |Puzzle precompute time: 917
2020-03-31 11:33:02.020181|INFO |FileManager | |listening on 0.0.0.0:30033, [::]:30033
2020-03-31 11:33:02.096402|INFO |Query | |listening for query on 0.0.0.0:10011, [::]:10011
2020-03-31 11:33:02.097017|INFO |Query | |listening for ssh query on 0.0.0.0:10022, [::]:10022
2020-03-31 11:33:02.097146|INFO |CIDRManager | |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128,
2020-03-31 11:33:02.229599|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2020-03-31 11:37:07.941797|INFO |ServerMain | |Received signal SIGTERM, shutting down.
So yeah, bascially its not really a crash, but its getting killed right on start.
While starting it over YATQA everything runs smooth. No errors or anything.
And i’m not quite sure in which logs i have to look, to find out why the operating system sent the kill command.
Greetings, and thanks for your help!
Yes log 0 is the right one where you see the reason.
SIGTERM Could be anything.
The console where command was send does close and all processes that where started in that console or a script is running doing that or script preventing to run the server that way etc.
Renamed title of thread.
Yeah, but that’s the log that i sent you. So, i don’t really know what to do now.
And why does it work with YATQA then? But not the normal way u would start the server?
Yes you did and there you see the more than once mentioned SIGTERM.
I do not know what on your system sends the SIGTERM to the TS server process. I gave you examples above.
The TS server only follows what the system tells the process.
Can not answer YATQA questions. Its not our software. It’s a 3rd party application.