TeamSpeak plugin "unexpected EOF" error

(2 Kommentare) (0 Reaktionen) (1 zugewiesene Person)Go (5.836 Forks)batch import

bughelp wantedsize/swaiting for response

Repository-Metriken

Stars: (17.756 Sterne)
PR-Merge-Metriken: (Durchschn. Merge 2T 12h) (136 gemergte PRs in 30 T)

Beschreibung

Relevant telegraf.conf

[[inputs.teamspeak]]
  server = "teamspeak-host:10011"
  username = "monitoring"
  password = "MY_PASSWORD"
  nickname = "telegraf"
  [inputs.teamspeak.tags]
    service = "teamspeak"

Logs from Telegraf

2024-08-13T15:49:30Z E! [inputs.teamspeak] Error in plugin: unexpected EOF

System info

telegraf 1.31.2

Docker

No response

Steps to reproduce

Restart the telegraf service
Notice "nickname is already in use" error
After a while, the error transforms to "Error in plugin: unexpected EOF"

Expected behavior

The plugin should disconnect from ServerQuery gracefully in order to "free" the nickname.

Actual behavior

Nickname isn't freed. Potentially causing the EOF error down the line.

Additional info

Sometimes when telegraf is restarted, it has trouble connecting to the same TeamSpeak server because "nickname is already in use". The errors might be related.

Contributor Guide

Research-Richtung: Investigate the TeamSpeak input plugin code (likely in plugins/inputs/teamspeak/) to understand how connections are managed. Focus on the disconnect logic when Telegraf stops or restarts. Ensure the plugin sends a proper ServerQuery quit command to free the nickname. Also check if there is a connection pool or reuse issue that causes the EOF error.
Tech Stack: go
Domain: backend
Issue Type: Fehler
Schwierigkeit: 3
Geschätzte Zeit: Halber Tag
Aktivitätsstatus: Blockiert
Klarheit: Klar
Voraussetzungen: GoTelegraf plugin developmentTCP networkingTeamSpeak ServerQuery
Einsteigerfreundlichkeit: 60