Some help "Received signal SIGTERM, shutting down."

[Santiago]

I have a problem with my server. Unfortunately the server is closed.
I've tried everything.
My log.

2016-02-10 11:22:11.446342|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.12.1 (2016-02-08 15:34:38)
2016-02-10 11:22:11.446448|INFO |ServerLibPriv | |SystemInformation: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 Binary: 64bit
2016-02-10 11:22:11.446474|INFO |ServerLibPriv | |Using hardware aes
2016-02-10 11:22:11.447153|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
2016-02-10 11:22:11.447185|INFO |DatabaseQuery | |dbPlugin version: 3.8.6
2016-02-10 11:22:11.447353|INFO |DatabaseQuery | |checking database integrity (may take a while)
2016-02-10 11:22:13.094783|INFO |Accounting | |Licensing Information
2016-02-10 11:22:13.094837|INFO |Accounting | |type : Non-profit
2016-02-10 11:22:13.094859|INFO |Accounting | |starting date : Fri Jan 1 00:00:00 2016
2016-02-10 11:22:13.094889|INFO |Accounting | |ending date : Wed Jul 6 00:00:00 2016
2016-02-10 11:22:13.094901|INFO |Accounting | |max virtualservers: 10
2016-02-10 11:22:13.094912|INFO |Accounting | |max slots : 512
2016-02-10 11:22:13.864007|INFO | | |Puzzle precompute time: 763
2016-02-10 11:22:13.864189|INFO |FileManager | |listening on xxx.xxx.xxx.xxx:xxxxx
2016-02-10 11:22:14.439457|INFO |CIDRManager | |updated query_ip_whitelist ips: 127.0.0.1,
2016-02-10 11:22:14.440000|INFO |Query | |listening on xxx.xxx.xxx.xxx:xxxxx
2016-02-10 11:22:15.388265|INFO | | |Increased protection level to: 1
2016-02-10 11:22:43.908649|INFO |ServerMain | |Received signal SIGTERM, shutting down.

The problem is "|INFO |ServerMain | |Received signal SIGTERM, shutting down."
I've looked in the forum of TeamSpeak, but their response is "Please do not host a server if you don't know what you are doing ;("

http://forum.teamspeak.com/threads/104872-Server-shutdown-quot-SIGTERM-quot

They say the problem is the OOM Killer - http://linux-mm.org/OOM_Killer
Even disabled yet the server and closed in up to 1 day
The only way I could solve and switching to Windows, more Windows is easily brought down by DDoS

 

[Kaptan647]

SIGTERM is the kill signal. It says proccess to kill itself. More info about SIGTERM:

Spoiler

Anytime you use kill on a process, you’re actually sending the process a signal (in almost all situations – I’ll get into that soon). Standard C applications have a header file that contains the steps that the process should follow if it receives a particular signal. You can get an entire list of the available signals on your system by checking the man page for kill.

Consider a command like this:

kill 2563

This would send a signal calledSIGTERM to the process. Once the process receives the notice, a few different things can happen:

the process may stop immediatelythe process may stop after a short delay after cleaning up resourcesthe process may keep running indefinitely

The application can determine what it wants to do once a SIGTERM is received. While most applications will clean up their resources and stop, some may not. An application may be configured to do something completely different when a SIGTERM is received. Also, if the application is in a bad state, such as waiting for disk I/O, it may not be able to act on the signal that was sent.

 

[Santiago]

Okay, but I do not understand what is causing it.

Another strange thing is that the server continues to run in "htop" with pid, but can not connect in query

The machines are virtualized VM, but so mine has this problem. The only difference is that much use the query with php integration. I do not know what else to do.

 

[Kaptan647]

Re-install your VM