Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug]: Using systemd to run ts3server on boot, myTeamSpeak ID is invalid

Abierto
#4,781 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
bash, linux, shell

Línea de trabajo

Comienza con la unidad de systemd mostrada en el issue y el punto de entrada de LinuxGSM ts3server start; después compara los logs del arranque y del reinicio manual, especialmente los mensajes sobre listas de revocación y resolución de nombres de host. Se considera completado cuando el servidor iniciado mediante systemd puede validar IDs de myTeamSpeak sin requerir un reinicio manual; el issue no identifica archivos del repositorio ni tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

command: start distro: Debian engine: null game: Teamspeak 3 info: systemd type: bug
User story

As a TeamSpeak 3 administrator, I want to start my ts3server without any error, or limitation in myTeamSpeak related services.

Game

Teamspeak 3

Linux distro

Debian 12

Command

command: start

Further information

When I connect to my TeamSpeak server:

<20:14:54> The TeamSpeak server could not validate your myTeamSpeak ID. Some myTeamSpeak related services are not available.
<20:14:54> Reconnecting might solve the issue.
<20:14:54> myTeamSpeak ID is invalid

Image

To fix, I have to manually restart the ts3server:

$ ./ts3server restart
[  OK  ] Stopping ts3server: Graceful: CTRL+c: 2 ... OK
[  OK  ] Starting ts3server: Applying Delete file /dev/shm/7gbhujb54g8z9hu43jre8 fix: TeamSpeak 3
[  OK  ] Starting ts3server: LinuxGSM

After that, connecting to the server, and the error message is gone.

My ts3server.service:

[Unit]
Description=LinuxGSM TeamSpeak 3 Server
After=network-online.target
Wants=network-online.target

[Service]
Type=forking
User=ts3server
WorkingDirectory=/home/ts3server
#Assume that the service is running after main process exits with code 0
RemainAfterExit=yes
ExecStart=/home/ts3server/ts3server start
ExecStop=/home/ts3server/ts3server stop
Restart=no

[Install]
WantedBy=multi-user.target
Relevant log output
# systemctl status ts3server
● ts3server.service - LinuxGSM TeamSpeak 3 Server
     Loaded: loaded (/etc/systemd/system/ts3server.service; enabled; preset: enabled)
     Active: active (exited) since Wed 2025-05-07 17:28:16 CEST; 2h 59min ago
   Main PID: 1655 (code=exited, status=0/SUCCESS)
        CPU: 1min 16.054s

May 07 17:28:13 PRECISION-5820 systemd[1]: Starting ts3server.service - LinuxGSM TeamSpeak 3 Server...
May 07 17:28:16 PRECISION-5820 ts3server[616]: [156B blob data]
May 07 17:28:16 PRECISION-5820 systemd[1]: Started ts3server.service - LinuxGSM TeamSpeak 3 Server.

/log/console/ts3server-console.log

2025-05-07 15:28:15.687430|INFO    |ServerLibPriv |   |TeamSpeak 3 Server 3.13.7 (2022-06-20 12:21:53)
2025-05-07 15:28:15.687486|INFO    |ServerLibPriv |   |SystemInformation: Linux 6.1.0-34-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.135-1 (2025-04-25) x86_64 Binary: 64bit
2025-05-07 15:28:15.687500|INFO    |ServerLibPriv |   |Using hardware aes
2025-05-07 15:28:15.690101|INFO    |DatabaseQuery |   |dbPlugin name:    SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
2025-05-07 15:28:15.690123|INFO    |DatabaseQuery |   |dbPlugin version: 3.11.1
2025-05-07 15:28:15.692662|INFO    |DatabaseQuery |   |checking database integrity (may take a while)
2025-05-07 15:28:15.706462|WARNING |Accounting    |   |Unable to open licensekey.dat, falling back to limited functionality
2025-05-07 15:28:15.708277|INFO    |Accounting    |   |Licensing Information
2025-05-07 15:28:15.708294|INFO    |Accounting    |   |licensed to       : Anonymous
2025-05-07 15:28:15.708303|INFO    |Accounting    |   |type              : No License
2025-05-07 15:28:15.708313|INFO    |Accounting    |   |starting date     : Tue Feb  1 00:00:00 2022
2025-05-07 15:28:15.708322|INFO    |Accounting    |   |ending date       : Thu Jul  1 00:00:00 2027
2025-05-07 15:28:15.708330|INFO    |Accounting    |   |max virtualservers: 1
2025-05-07 15:28:15.708337|INFO    |Accounting    |   |max slots         : 32
2025-05-07 15:28:16.107211|INFO    |              |   |Puzzle precompute time: 386
2025-05-07 15:28:16.107630|INFO    |FileManager   |   |listening on 0.0.0.0:30033, [::]:30033
2025-05-07 15:28:16.108086|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.108106|ERROR   |              |   |Could not open default UDP connection for weblist
2025-05-07 15:28:16.108220|INFO    |Query         |   |Using a query thread pool size of 2
2025-05-07 15:28:16.111244|INFO    |ServerLibPriv |   |failed to download revocation list - count: 1
2025-05-07 15:28:16.113380|INFO    |ServerLibPriv |   |failed to download revocation list - count: 1
2025-05-07 15:28:16.117284|INFO    |VirtualServerBase|1  |listening on 0.0.0.0:9987, [::]:9987
2025-05-07 15:28:16.117375|INFO    |Query         |   |listening for query on 0.0.0.0:10011, [::]:10011
2025-05-07 15:28:16.118829|INFO    |Query         |   |listening for ssh query on 0.0.0.0:10022, [::]:10022
2025-05-07 15:28:16.118860|INFO    |Query         |   |listening for http query on 0.0.0.0:10080, [::]:10080
2025-05-07 15:28:16.118987|INFO    |CIDRManager   |   |updated query_ip_allowlist ips: 127.0.0.1/32, ::1/128,
2025-05-07 15:28:16.207731|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.210957|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.211023|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.211093|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.211157|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.211222|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.211288|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.211358|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:28:16.211423|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
...
2025-05-07 15:28:16.214374|ERROR   |              |   |Could not open/bind UDP connection on 0.0.0.0 for weblist. Using default
2025-05-07 15:28:16.314586|ERROR   |              |   |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 11
2025-05-07 15:38:16.003923|ERROR   |              |   |TS3ANetwork::Send failed error: 111
2025-05-07 15:38:18.003917|ERROR   |              |   |TS3ANetwork::Send failed error: 111
2025-05-07 15:48:14.297865|ERROR   |              |   |TS3ANetwork::Send failed error: 111
2025-05-07 15:48:16.027029|ERROR   |              |   |TS3ANetwork::Send failed error: 111
2025-05-07 15:48:18.003917|ERROR   |              |   |TS3ANetwork::Send failed error: 111
2025-05-07 15:58:14.297657|ERROR   |              |   |TS3ANetwork::Send failed error: 111
2025-05-07 18:08:16.003919|ERROR   |              |   |TS3ANetwork::Send failed error: 111
...
2025-05-07 18:14:51.553059|INFO    |VirtualServerBase|1  |rejecting myteamspeakid: revoke list out of date
2025-05-07 18:14:51.553099|INFO    |VirtualServerBase|1  |client is connecting with a invalid or revoked myTeamSpeak ID
2025-05-07 18:14:52.169044|INFO    |VirtualServerBase|1  |rejecting myteamspeakid: revoke list out of date
2025-05-07 18:14:52.169074|INFO    |VirtualServerBase|1  |failed to update myTeamSpeak ID
2025-05-07 18:18:16.003919|ERROR   |              |   |TS3ANetwork::Send failed error: 111
2025-05-07 18:25:50.337136|INFO    |ServerMain    |   |Received signal SIGINT, shutting down.
2025-05-07 18:25:50.337371|INFO    |VirtualServerBase|1  |stopped

/log/server/ts3server_2025-05-07__18_44_44.866282_1.log

2025-05-07 18:44:45.183112|INFO    |VirtualServerBase|1  |listening on 0.0.0.0:9987, [::]:9987
2025-05-07 18:44:50.614573|INFO    |VirtualServerBase|1  |rejecting myteamspeakid: revoke list out of date
2025-05-07 18:44:50.614609|INFO    |VirtualServerBase|1  |client is connecting with a invalid or revoked myTeamSpeak ID
2025-05-07 18:44:51.087669|INFO    |VirtualServerBase|1  |rejecting myteamspeakid: revoke list out of date
2025-05-07 18:44:51.087692|INFO    |VirtualServerBase|1  |failed to update myTeamSpeak ID
2025-05-07 18:45:11.645216|INFO    |VirtualServerBase|1  |rejecting myteamspeakid: revoke list out of date
2025-05-07 18:45:11.645243|INFO    |VirtualServerBase|1  |client is connecting with a invalid or revoked myTeamSpeak ID
2025-05-07 18:45:12.165855|INFO    |VirtualServerBase|1  |rejecting myteamspeakid: revoke list out of date
2025-05-07 18:45:12.165879|INFO    |VirtualServerBase|1  |failed to update myTeamSpeak ID

After successful restart:

2025-05-07 18:25:54.930535|INFO    |DatabaseQuery |   |dbPlugin name:    SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
2025-05-07 18:25:54.930553|INFO    |DatabaseQuery |   |dbPlugin version: 3.11.1
2025-05-07 18:25:54.930654|INFO    |DatabaseQuery |   |checking database integrity (may take a while)
2025-05-07 18:25:54.938711|WARNING |Accounting    |   |Unable to open licensekey.dat, falling back to limited functionality
2025-05-07 18:25:54.938907|INFO    |Accounting    |   |Licensing Information
2025-05-07 18:25:54.938925|INFO    |Accounting    |   |licensed to       : Anonymous
2025-05-07 18:25:54.938935|INFO    |Accounting    |   |type              : No License
2025-05-07 18:25:54.938945|INFO    |Accounting    |   |starting date     : Tue Feb  1 00:00:00 2022
2025-05-07 18:25:54.938954|INFO    |Accounting    |   |ending date       : Thu Jul  1 00:00:00 2027
2025-05-07 18:25:54.938961|INFO    |Accounting    |   |max virtualservers: 1
2025-05-07 18:25:54.938969|INFO    |Accounting    |   |max slots         : 32
2025-05-07 18:25:55.327308|INFO    |              |   |Puzzle precompute time: 377
2025-05-07 18:25:55.327459|INFO    |FileManager   |   |listening on 0.0.0.0:30033, [::]:30033
2025-05-07 18:25:55.349656|INFO    |Query         |   |Using a query thread pool size of 2
2025-05-07 18:25:55.357425|INFO    |VirtualServerBase|1  |listening on 0.0.0.0:9987, [::]:9987
2025-05-07 18:25:55.357511|INFO    |Query         |   |listening for query on 0.0.0.0:10011, [::]:10011
2025-05-07 18:25:55.357598|INFO    |Query         |   |listening for ssh query on 0.0.0.0:10022, [::]:10022
2025-05-07 18:25:55.357629|INFO    |Query         |   |listening for http query on 0.0.0.0:10080, [::]:10080
2025-05-07 18:25:55.357664|INFO    |CIDRManager   |   |updated query_ip_allowlist ips: 127.0.0.1/32, ::1/128,
2025-05-07 18:25:55.482686|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2025-05-07 18:30:57.003922|ERROR   |              |   |TS3ANetwork::Send failed error: 111
2025-05-07 18:30:59.003916|ERROR   |              |   |TS3ANetwork::Send failed error: 111
Steps to reproduce
  1. Use systemd to run the server on boot: https://docs.linuxgsm.com/configuration/running-on-boot
  2. Connect to your ts3server
  3. see error message
Lenguaje dominante
Shell
Estrellas
4.9k
Forks
870
Merge medio
14 h 50 min
PR fusionados (30 d)
109

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de GameServerManagers/LinuxGSM

Todos los issues de GameServerManagers/LinuxGSM

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.