Very simple server auto start method and crash restart script (root & non-root)

[Arandas]

Here is a simple script I wrote to automatically start a TS3 server on boot and auto restart after a crash. Tested with CentOS 5.x and Ubuntu 10 & 11, but should work with most distros.

For x86:

#!/bin/bash

TEAMSPEAK=`ps ax | grep ts3server_linux_x86 | grep -v grep | wc -l`

if [ $TEAMSPEAK -eq 1 ]
then
exit
else
cd /path/to/teamspeak ; ./ts3server_startscript.sh start
fi

For x64:

#!/bin/bash

TEAMSPEAK=`ps ax | grep ts3server_linux_amd64 | grep -v grep | wc -l`

if [ $TEAMSPEAK -eq 1 ]
then
exit
else
cd /path/to/teamspeak ; ./ts3server_startscript.sh start
fi

Change "/path/to/teamspeak" to your actual TeamSpeak directory.

Script is also included as an attachment at the bottom, simply put it in a directory on your server (such as the teamspeak directory).

Login as the user you wish to run this as, this does not have to be root. In crontab add a line such as this:

*/2 * * * * sh /path/to/script/script.sh

Where */2 is 2 minutes, change to */5 for 5 minutes.. and so on. This is after how many minutes to check if the server is running, and if not to attempt to start it.

This works best when you have an additional line in crontab like:

@reboot cd /path/to/teamspeak ; ./ts3server_startscript.sh start

Again changing the path. This will start the server automatically after boot (otherwise you would have to wait for the script to run after boot). TeamSpeak server will then run as the same user who added the crontab entries.

A thing to note, you may have to comment the script line in crontab with # when updating the TeamSpeak server so it doesn't automatically start it. Then uncomment it again after. There is also a limitation, if the server won't start due to error it will keep attempting to start it.

Disclaimer: Though this script was created by me, I accept no responsibility for data loss or damage by the use of the script though it should be perfectly safe to use.

Attached file is for x86 server version, for x64 change line 3 from "ts3server_linux_x86" to "ts3server_linux_amd64".

[Lupus42]

I know, I'm practicing thread necromancy, since no one has posted to this thread in more than 2 months, but I just wanted to tell the OP Thank you. Thanks a ton. You solved a problem that stopped me from trying to run my own TS3 server 2 years ago. and you explained it nicely with an attached cron job I was actually able to use as well. Thank you so very much. Someone sticky this please.

[Bobbi]

This is perfect, well explained and very easy to implement. Thanks for the file too.

I have been looking for months for this. Thank you so much.

I agree this definately deserves a sticky.

[tictac22]

This looks like exactly what im looking for but im running in to an issue, if i had my script.sh stored in my Teamspeak Directory at /home/teamspeakserver would the path to teamspeak be /home/teamspeakserver/teamspeak3-server_linux-x86 or just /teamspeak3-server_linux-x86 ?

[SilentStorm]

Nope needs to be the full path.

[LS_ARRoW]

Thanks Arandas this is 100% working
for boot system, and when TeamSpeak is stopped just worked.

I recommend!

[Ar2rJke]

how do I:

#!/bin/bash

TEAMSPEAK=`ps ax | grep ts3server_linux_x86 | grep -v grep | wc -l`

if [ $TEAMSPEAK -eq 1 ]
then
exit
else
cd /home/archi/teamspeak3-server_linux-x86 ; ./ts3server_startscript.sh start

crontab:

*/2 * * * * cd ~/scripts && sh crash.sh

as a result of the logs, I:

Jul 16 10:08:01 ts3 /USR/SBIN/CRON[5721]: (CRON) error (grandchild #5725 failed with exit status 1)
Jul 16 10:08:01 ts3 /USR/SBIN/CRON[5721]: (CRON) info (No MTA installed, discarding output)

after commenting in the crontab "#" of a script error no!

Question! what's the problem?

[MudGuts]

AFAIK another script isn't necessary and you can just cron the start script itself?

Please correct me if I am wrong.