• Be part of the TeaParty!
    Click here for more information

Information [Linux] How to update your TeaSpeak server (including script)

essem

Active member
0. (Only once required)
You can download the Updatescript with this command
Code:
wget https://raw.githubusercontent.com/essemX/teaspeak-updatescript/master/update2.sh
or
create a new File and copy/paste it from the link.

If you don't have curl installed, its required and recommended:
Code:
apt-get update
apt-get install curl
1.
Stop your TeaSpeak-server (if not already done).
Depending on how you started your server either
Code:
./teastart.sh stop
or
Code:
screen -r
CTL+C
(or something completly different)
can be used.

2.
Run the script:
Code:
sh update.sh
Run the Update-script in the same directory where TeaSpeaks startscripts are.

Alternatively you can do it manually (replace TeaSpeak-X.X.X with the version you want from here)
Code:
wget https://repo.teaspeak.de/server/linux/amd64/TeaSpeak-X.X.X.tar.gz
tar -xzf TeaSpeak-X.X.X.tar.gz
rm TeaSpeak-X.X.X.tar.gz
3.
Start your Server again.
Again depending on how you run your server:
Code:
screen -S teaspeak sh teastart_minimal.sh
or
Code:
./teastart.sh start
(or something completly different)

2018/04/20: Updated the script. If it dosn't work, repeat step 0. to get the new version.
2018/05/04: Removed the build Argument and made it cleaner. Old script is still available here.
2018/06/12: Added a little backup functionality for config and database and make scripts executable for owner. Thanks to @Bluscream
2018/08/10: Updated repo.
2018/08/12: Script now checks the environment (64 vs 32 bit)
2019/05/18: Updated script to new version system
 
Last edited:

knightnato

New member
after i did the update i'm getting these:
Code:
<16:09:41> file not exists
<16:09:44> file not exists
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
 

essem

Active member
after i did the update i'm getting these:
Code:
<16:09:41> file not exists
<16:09:44> file not exists
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
<16:09:48> not implemented
thats weird and has nothing todo with the update script rather than with teaspeak.
you can contact @WolverinDEV if you got issues on the actual teaspeak server.
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Hmm based on the first two errors I think it's the ftstop command, so your client tries to download non existing files.
But if you want to be sure wich commands fails, you have to look at the log
 

h1web

Well-known member
It would be cool that we can assign a Servermessage before the Server quits :-D like "Server is back in 10 seconds for upgrades."
 

essem

Active member
well, as far as i know you can stop the server with a custom message or at least change the config message.
my script does not include a restart part because of the amount of different ways to do it.
 

essem

Active member
@h1web updated the script so it checks if the environent is 32 or 64 bit and use the corresponding version.

Hopefully it is fine with every linux distribution, could just test it on my two 64bit machines.
 

Tincho

Active member
@h1web updated the script so it checks if the environent is 32 or 64 bit and use the corresponding version.

Hopefully it is fine with every linux distribution, could just test it on my two 64bit machines.
Hi. Thanks for the script. On 64 bit is working fine. Just one question, could you add a validation to stop the script if server is actually on lastest version?
 

h1web

Well-known member
Really offtopic, but do you also have a TeamSpeak Update Script like that? I really like it.
 

razaq

Well-known member
just for clarification: Your script backs up the db and config
Code:
cp config.yml config.yml.old
cp TeaData.sqlite TeaData.sqlite.old
Since they should be compatible between the versions, why dont you copy them back after the unpacking?