Completed Server not responding after several hours uptime

[DrN00bish]

How many connections have you set to be used?
Your database string should end with something like &connections=X where X=number of connections. I run 10 since I noticed the old TS3 server had around that amount of open connections to the DB.

 

[dspcorp]

i use 4, i change for 10.

Uptime:3 hours 45 minutes 7 seconds
New Uptime:0 hours 0 minutes 13 seconds

i wait for others crash or down.

- settings modified to &connections=10.
- hosts and iptables block Tea*Speak official.
127.0.0.1 Tea*Speak.com
127.0.0.1 accounting.Tea*Speak.com
127.0.0.1 backupaccounting.Tea*Speak.com
127.0.0.1 accounting2.Tea*Speak.com
127.0.0.1 blacklist.Tea*Speak.com
127.0.0.1 blacklist2.Tea*Speak.com
127.0.0.1 ipcheck.Tea*Speak.com
127.0.0.1 ocsp.digicert.com
127.0.0.1 hardy.Tea*Speak.4players.de
::1 Tea*Speak.com
::1 accounting.Tea*Speak.com
::1 backupaccounting.Tea*Speak.com
::1 blacklist.Tea*Speak.com
::1 ipcheck.Tea*Speak.com
::1 ocsp.digicert.com
::1 hardy.Tea*Speak.4players.de

- mysql server setup modified.
key_buffer_size = 32M
max_allowed_packet = 32M
thread_stack = 192K
thread_cache_size = 16
myisam_recover_options = BACKUP
max_connections = 200
table_cache = 128
thread_concurrency = 20
query_cache_limit = 16M
query_cache_size = 32M

 

[lvlkoo]

Using 1.2.13-b6, 4 days online. No crashes, low memory usage.
PS. using mysql

 

[DrN00bish]

ocsp.digicert.com

Personally I wouldn't block this one since it's a general provider of certificates and it might end up giving you a hard time at some point when needing to renew, update or check some certificates.

Also at some point you might want to comment out the thread_concurrency = 20 unless you have a high load on your databases (in which case you'd probably use some loadbalancing combined with spreading out databases on multiple servers anyway).... You don't have to change this though.

And as an additional info. I noted somewhere at some point if you're using the AccountingServerEmulator-Linux from r4p3 I had trouble on my ipv6 servers as soon as I added the ipv6 entries of accounting and backupaccounting. This was bonusinfo though because it has nothing to do with TeaSpeak lol

Edit:
In any case it seems like there might be a general issue for some people with crashing's currently so I can only urge you to stay updated and update the TeaSpeak server version as soon as it's possible when the new fixes gets rolled out.

 

[dspcorp]

i use version 1.2.15-b6 i try for 1.2.13-b6

teaspeak@TEASPEAK:~$ wget https://repo.teaspeak.de/server/linux/amd64/TeaSpeak-1.2.13-beta-6.tar.gz
--2018-09-03 12:10:02-- https://repo.teaspeak.de/server/linux/amd64/TeaSpeak-1.2.13-beta-6.tar.gz
Résolution de repo.teaspeak.de (repo.teaspeak.de)… 104.18.35.91, 104.18.34.91, 2400:cb00:2048:1::6812:225b, ...
Connexion à repo.teaspeak.de (repo.teaspeak.de)|104.18.35.91|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 21989535 (21M) [application/octet-stream]
Sauvegarde en : « TeaSpeak-1.2.13-beta-6.tar.gz »

TeaSpeak-1.2.13-beta-6.tar.gz 100%[==================================================================================>] 20,97M 71,0MB/s in 0,3s

2018-09-03 12:10:02 (71,0 MB/s) — « TeaSpeak-1.2.13-beta-6.tar.gz » sauvegardé [21989535/21989535]

teaspeak@TEASPEAK:~$ tar xvf TeaSpeak-1.2.13-beta-6.tar.gz
teaspeak@TEASPEAK:~$ ./teastart_autorestart.sh start
teaspeak@TEASPEAK:~$ uname -a
Linux TEASPEAK 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 GNU/Linux

Downgrade done. i wait next crash xD

 

[mkll11one]

it's not recommended to use the 1.2.15-b6 because issues. better to downgrade. ^^

 

[mola19]

Using 1.2.13-b6, 4 days online. No crashes, low memory usage.
PS. using mysql

I have some questions.

How much RAM is low RAM usage?
How many users do you have connected to the server?

 

[dspcorp]

32 gb ram
4 cores 4 threads
Debian 9 64bits last version
i am connected just me and 1 friends = 2 clients / 512 slots

 

[mola19]

32 gb ram
4 cores 4 threads
Debian 9 64bits last version
i am connected just me and 1 friends = 2 clients / 512 slots

Hmmm, it is normal that a server with 2 users does not crash, the problem for me starts with the 60/70 users online.

 

[Saci]

dspcorp

Have your resources reached the limit? check it
if you used autostart in a few seconds it automatically restarts the server after a critical error that causes it to shut down

 

[dspcorp]

What is the limit of teaspeak? and yes it restarts automatically.

 

[lvlkoo]

I have some questions.

How much RAM is low RAM usage?
How many users do you have connected to the server?

Around 400 mb for 100 users connected

 

[dspcorp]

Version:TeaSpeak on Linux
License:Non-Profit License
Address:xxx
Uptime:8 hours 18 minutes 24 seconds

Current Clients:4 / 512 (-1 reserved)
Current Channels:11

No crash again i wait

 

[WolverinDEV]

Server hangup should be fixed within build 5 (I recommend to use build 7!)

Memory issue is already another thread