Received signal SIGTERM, shutting down

**casperinmd** · 06-04-2010, 00:03

Ok, so I found this thread: http://forum.teamspeak.com/showthrea...hlight=SIGTERM

But his answer was the host was shutting down for maintenance. I contacted my host, Bluehost, adn while they don't support running TS, they allow it and have a KB article on setting it up.

I ran TS2 for years, but TS3 seems to shut down a lot on me with this message, and it seems to be frequently now.

My host support said they do not block it and are not shutting it down. Is there anything else that can cause this even in the logs? Can I enable more logging to see why it is being sent the kill sig?

Thanks for any ideas.

Error:

**FH3095** · 06-04-2010, 07:19

Originally Posted by casperinmd

Can I enable more logging to see why it is being sent the kill sig?

No, you can't, because Teamspeak gets the kill signal from Linux. Teamspeak doesn't know why it recieves a kill signal, because Linux doesn't tell Teamspeak that.
Normaly Linux has two reasons for sending a kill signal:
1.: When the server shuts down.
2.: When someone uses the kill or killall command in ssh.
So I think one of these two things happen.

**casperinmd** · 06-04-2010, 11:55

Thanks. I will now follow up with host to let them know they need to figure it out as to what is killing the process.

**TheMinz** · 06-04-2010, 12:02

There is actually a third possibility where this could come from :
If you are running Teamspeak on a Vserver (virtual rootserver etc.), it is very likely that your system ressources have very thight soft and hard-limits.
Once these limits are hit the OS will automatically shutdown programms with lower priority to keep the high priority ones running.
I suggest you take a look at your system ressources when launching TS3, especially system memory.

**Trashman992** · 21-05-2010, 13:43

I have this issue too. I think it happens when the server runs out of RAM.

What do I have to change to get the server to decide not to shut down TS3 when it goes looking for processes to kill?

How do I increase teamspeak's priority?

**Peter** · 21-05-2010, 14:09

http://linux-mm.org/OOM_Killer

**LordISP** · 03-06-2010, 22:38

Originally Posted by Peter

http://linux-mm.org/OOM_Killer

Thank you for this information, but could you kindly explain what exactly I have to do with OOM_Killer

Thanks in advanced

Lord ISP

**Trashman992** · 04-06-2010, 00:50

What I learnt:
When the server runs critically low on RAM OOM Killer kills a process it selects based upon an arcane criteria I don't understand. You can immunise a chosen process (like teamspeak) against this. The instructions are fairly clear here:
http://linux-mm.org/OOM_Killer

However.
I don't recommend doing this. If you prevent OOM killer killing Teamspeak, the largest memory user at the time, OOM killer will go through your server picking the next most favourable process, and the next, and the next, each time freeing up more memory for TS to grow into. OOM killer was killing almost every other process on my server: Apache, MySQL, Mail server, FTP daemon etc.

I found a better solution by creating a cronjob that checks every 60 seconds if Teamspeak is running, and if it isn't, start it. If you'd like, I can link what I use.

A better better solution.
Get a server from someone who isn't Goddaddy; someone who will let you add memory without re-renting it.

**Todd Edwards** · 05-06-2010, 02:22

Originally Posted by Trashman992

I found a better solution by creating a cronjob that checks every 60 seconds if Teamspeak is running, and if it isn't, start it. If you'd like, I can link what I use.

Please link it.

...T.

**Trashman992** · 06-06-2010, 04:04

DISCLAIMER: I am a teamspeak user, not a linux or teamspeak guru or employee. Follow the directions here at your own risk and follow the golden rule of IT:
If it ain't broke, don't f*** with it.

How to get Teamspeak3 to restart automatically when it crashes:
Alrighty.

I'm using Centos Linux (A variation on Redhat) - if you are using something different then these instructions might not work. You will need the TS3 Startup Script. It comes with the TS3 server and is called:

ts3server_startscript.sh

Edit it in your favourite editor as root or by sudoing up.
Eg.

User@server$ sudo nano ts3server_startscript.sh

At the start, under

Code:

#!/bin/bash
# Copyright (c) 2010 TeamSpeak Systems GmbH
# All rights reserved

Add these lines:

Code:

# Startup script for teamspeak3
#
# chkconfig: 2345 80 20
# description: Modified Startup Script for teamspeak3.

Save it to /etc/init.d/teamspeak3 (ctrl+o in nano).

Now we set up the cron job to run it. This is Chris Childers' Cron job I found on these forums, which I have modified a little to output a logfile.

User@server$ cd ~
User@server$ nano ts3autorestart.sh

Paste this into nano.

Code:

#! /bin/sh
#
# TeamSpeak Cron Job
# Author: Chris Childers
# E-Mail: Chris@darkstarllc.com
# Address: http://www.darkstarllc.com
#

### Set your default TS Root Directory
tsdir="/usr/teamspeak3"

### Set your TS Binary Name
tsbin="ts3server_linux_x86"

### Set your TS Pid File
tspid="ts3server.pid"

###
logfile="~/autorestart.log"

########## you probably don't need to change anything below here ##########

cd $tsdir

# is there a pid file?
if test -r $tspid
then
  # there is a pid file -- is it current?
  pid=`cat $tspid`
  if `kill -CHLD $pid >/dev/null 2>&1`
  then
    echo "TeamSpeak is currently running...."
    exit 0
  fi
  echo ""
  echo "$(date) || Stale $tspid file, erasing..." >> $logfile
  rm -f $tspid >> $logfile
  echo "$(date) || Attempting to Restart TeamSpeak" >> $logfile
/etc/init.d/teamspeak3 start >> $logfile
else
echo "$(date) || $tspid appears to be missing. Attempting to Restart TeamSpeak" >> $logfile
/etc/init.d/teamspeak3 start >> $logfile
fi

Save it and exit. Issue a chown command to give ownership to your teamspeak user. Eg:

User@server$ sudo chown teamspeak:teamspeak ts3autorestart.sh

Now all you have to do is define the cronjob. You will need to run the cronjob as the user teamspeak, so:

User@server$ su teamspeak
User@server$ crontab -e

Hit s to enter insert mode in vi. Paste this.

Code:

*/1 * * * * ~/ts3autorestart.sh

Hit Esc to leave insert mode, and type :wq (colon w q) to "write and quit" from vi. If the vi editor in this step is giving you a headache, google is your friend.

User@server$ crontab -l
Should show you your new crontab entry, allowing you to confirm your success.

User@server$ logout

Takes you out of the user teamspeak's session and back to your own.

User@server$ ps aux | grep ts3server_linux

Will provide a screen like the following:

500 15816 0.1 0.6 30512 6748 ? Sl Jun02 6:49 ./ts3server_linux_x86 inifile=ts3server.ini
500 27997 0.0 0.0 1760 496 pts/0 S+ 19:54 0:00 grep ts3server_linux

The first entry lists 15816 as Teamspeak's PID. The second is the command you just issued and should be ignored.

Warning: the next step will shut down your teamspeak server (hopefully, you've done everything right and it will be back automatically in 60 seconds.)
User@server$ kill 15816

Wait 60 seconds, and try to connect to Teamspeak on your client PC. If all goes well, teamspeak will be running again courtesy of your cron job.

Troubleshooting:
If all does not go well, first try to isolate the problem by issuing

User@server$ /etc/init.d/teamspeak3 restart

and noting any error message before attempting to connect. If you can now connect, the crontab is broken. If you can't, the startup script is broken.

If the startup script is broken, edit it and check your ini file is set up correctly - this would be a common mistake.

Good luck, hope this helps someone - I spent half an hour of my life typing it up

**larshamm** · 07-08-2010, 09:04

Okay since the 2 lastest linux x86 beta Version i have problems with connecting to my V-Server running on Debian Lenny.

My Teamspeak 3 Client (current Version) disconnects after 5-10 minuts and a reconnect doesn't work.

I get this problem on every Server-Ports on my Teamspeak 3 Installation.

But the Server is even running -->./ts3server_startscript status...ist running every time.

But in the Server Log is the Error which i postes in the title here:

an this error in another Server Log:

Code:

2010-08-07 07:52:44.881368|INFO    |VirtualServer |  1| client disconnected 'Adm_Munro'(id:2) reason 'reasonmsg=connection lost'

Another problem is that the server logs pringt wrong times.

My Server log shows time like 07:52 but is 09:XX ?

**larshamm** · 07-08-2010, 09:09

yes...now and before beta 26...with the same problem...but there i have no logs because beta 27 is a re installation.

**larshamm** · 07-08-2010, 09:36

The logs shows the following with the minimal start script:

Code:

(c)TeamSpeak Systems GmbH

Logging started
2010-08-07 08:31:38.467589|INFO    |ServerLibPriv |   | Server Version: 3.0.0-beta27 [Build: 12002], Linux
2010-08-07 08:31:38.467887|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
2010-08-07 08:31:38.467965|INFO    |DatabaseQuery |   | dbPlugin version: 3.6.21
2010-08-07 08:31:38.468261|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
2010-08-07 08:31:38.481560|INFO    |SQL           |   | pruning old database log entries where timestamp is older than 90 days
2010-08-07 08:31:38.697910|INFO    |Accounting    |   | Licensing Information
2010-08-07 08:31:38.698523|INFO    |Accounting    |   | type              : Non-profit
2010-08-07 08:31:38.698984|INFO    |Accounting    |   | starting date     : Sun Dec 20 23:00:00 2009
2010-08-07 08:31:38.699522|INFO    |Accounting    |   | ending date       : Mon Dec 20 23:00:00 2010
2010-08-07 08:31:38.699757|INFO    |Accounting    |   | max virtualservers: 10
2010-08-07 08:31:38.699967|INFO    |Accounting    |   | max slots         : 512
2010-08-07 08:31:38.710724|INFO    |FileManager   |   | listening on 0.0.0.0:30033
2010-08-07 08:31:38.799314|INFO    |VirtualServer |  1| listening on 0.0.0.0:9987
2010-08-07 08:31:38.799684|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1,
2010-08-07 08:31:38.800362|INFO    |Query         |   | listening on 0.0.0.0:10011

connection: ok
But how can i run the Server every time ? The minimal script shutting down the Server when i close my SSH Putty Console ?

EDIT: Now...connection lost again...

**larshamm** · 07-08-2010, 13:48

Ok i lost the connection weh i am using /ts3server_minimal_runscript.sh too..

How can i check the Debian Ports ?

Or is this also a Teamspeak 3 Server or Client (Windows x64 Client)[ both current Version] problem ?

Its crazy because i could connect to another hosted Teamspeak 3 Server with current Version very well.

But my V-Server doesn't work correctly !

**larshamm** · 07-08-2010, 14:45

yes both are the lastest now. Client updatet. Server fresh Install.

other people are couln*t connect to server too.

Therefore i come to the conclusion that i must something with the Server or Installation and not with my local computer, thats why your link doesn't help.

Thread: Received signal SIGTERM, shutting down

Thread Tools

Rate This Thread

Display

Received signal SIGTERM, shutting down

[SOLVED] Received signal SIGTERM, shutting down

Received signal SIGTERM, shutting down.

How to get Teamspeak3 to restart automatically when it crashes

Received signal SIGTERM, shutting down ? Nor connect to Server

Thread Information

Users Browsing this Thread

Similar Threads

Debian, S3ANetwork::Bind failed error: 98 & Received signal SIGTERM, shutting down.

SIGTERM immediately on launch

Received signal SIGTERM, shutting down ? Nor connect to Server

[Solved] Signals SIGTERM; SIGHUP; Shutting Down

Posting Permissions