Well the service is imo the correct way to do it.
You have to create the service like shown in the tutorial. It should work.
You should run this before ./ts3server_startscript.sh start though:
chown -R teamspeak:teamspeak /home/teamspeak/
1 Like
Okay, I first sent the statement which you told me to send
After that, I sent the start statement to have the password and key.
Now, I am going to make the service as shown in that blog post.
But do you want to me to first connect to the teamspeak client and enter my key or I should make the service before connecting to the client?
Secondly, I should stop the server before making the service?
I’m little new in Linux that’s why I am facing issues.
Secondly, It is not going to the new line with the root… Should I press ctrl + C to go to the next line and do the service thing?
I followed the blog steps to make the service…
This is the error I get:
Okay, I first sent the statement which you told me to send
After that, I sent the start statement to have the password and key.
Now, I am going to make the service as shown in that blog post.
But do you want to me to first connect to the teamspeak client and enter my key or I should make the service before connecting to the client?
Secondly, I should stop the server before making the service?
I’m little new in Linux that’s why I am facing issues.
Secondly, It is not going to the new line with the root… Should I press ctrl + C to go to the next line and do the service thing?
I followed the blog steps to make the service…
This is the error I get:
There is something wrong I am doing or something wrong with the steps…
Because If I do this:
./ts3server_startscript.sh start
And then I make a service.
Auto-Start doesn’t work.
But if I skip the ./ts3server_startscript.sh start
and make service directly, auto-start works fine.
Yes sorry, my fault.
If you use the startscript to start the server it will not stop once it finished executing.
So you will have to stop it manually after starting it for the first time.
(service teamspeak stop)
When the service does not start and the status reports failure can you run journalctl -u teamspeak? This will show the log why it could not start.
2 Likes
Hmm, Can you do one thing. If you could send me the steps which would give me the password and key plus… it created the automated reboot stuff too?
I will do that directly and it will solve all the hassle.
I really appreciate your help in this.
Thanks.
Ok. I can’t test the service part as I only got the wsl right now but this should work:
sudo su -
yum -y update
yum install nano wget perl tar net-tools bzip2 -y
adduser teamspeak --disabled-login
cd /home/teamspeak
wget https://files.teamspeak-services.com/releases/server/3.12.1/teamspeak3-server_linux_amd64-3.12.1.tar.bz2
tar xvf teamspeak3-server_linux_amd64-3.12.1.tar.bz2
cd teamspeak3-server_linux_amd64 && mv * /home/teamspeak && cd .. && rm -rf teamspeak3-server_linux_amd64-3.12.1.tar.bz2
touch /home/teamspeak/.ts3server_license_accepted
chown -R teamspeak:teamspeak .
sudo -u teamspeak ./ts3server inifile=ts3server.ini
Ctrl+C
nano /etc/systemd/system/teamspeak.service
[Unit]
Description=TeamSpeak 3 Server
After=network.target
[Service]
WorkingDirectory=/home/teamspeak/
User=teamspeak
Group=teamspeak
Type=forking
ExecStart=/home/teamspeak/ts3server_startscript.sh start inifile=ts3server.ini
ExecStop=/home/teamspeak/ts3server_startscript.sh stop
PIDFile=/home/teamspeak/ts3server.pid
RestartSec=15
Restart=always
[Install]
WantedBy=multi-user.target
systemctl enable teamspeak.service
I am pretty sure that this should work. Tell me if it did (not).
1 Like
Thank you for the reply. I was reading this before implementing. I think you missed the part where we get the serverquery password or something?
Please check.
Sorry, I might be wrong.
Nope, it’s the last command from the first block
1 Like
Damn typo, fixed it
1 Like
Then just leave the disabled login and run the normal adduser teamspeak
1 Like
Yes, It worked. Not a mistake but to complete the process, we have to run systemctl start teamspeak.service so that TS starts.
Is it right what I have suggested or something I am missing?
Because without sending the above command, server wasn’t connecting.
do you know anything about the Server Permissions? ( [TS3] Permission Related Questions )
Yeah that’s true
enable just enables it to start when you reboot.
1 Like
Maybe I’ll check it out later. I think this was discussed already earlier on the forum.
Thanks for the help @Gamer92000 I can’t really thank enough for your efforts you have given. Yeah, I hope if you could help me into the permissions issue as well.
I’m willing to shift my small community to TS3 from Discord because we are bunch of people with slow PCs and Discord eats a lot of processing.
Will be waiting for your response over there.
I have one more question if you don’t mind.
I’m right now aiming for maximum 32 users only.
What amount of RAM, CPU (Cores or vCPU) is enough for the TeamSpeak with 32 Users max and min. both.
Thanks.
I had a server running on my RPi (1) B when it was new… This was not (and still is not) supported.
However it ran without any problems despite the back in the days not really good qemu emulator.
So there is no official recommendation afaik. By my personal experience I would recommend at least
2 vCores and at least 1 GB of RAM. Everything above should work without any problems.
1 Like
Hard to answer this one as precisely as people would like, but for 32 users/standard sqlite setup, ‘pretty much anything’. We recommend 1GB RAM, but for occasional use, I’d expect lower RAM/1 core setups to be fine. 2 cores will help.
For higher user counts (hundreds+), expect to see higher CPU usage and (of course) network, and that’s where better spec machines start to be helpful.
3 Likes
Hello, Thanks for the reply.
This is the specs of my server for TS.
I don’t know the definition of 1 vCPU here.
It’s Amazon Web Services LightSail.
@Gamer92000 @davinciTS (Tagging because I don’t know how to reply to multiple answers).
