influxdata/telegraf

TeamSpeak plugin "unexpected EOF" error

Closed

#15,738 opened on Aug 13, 2024

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Go (9,892 stars) (4,161 forks)batch import
bughelp wantedsize/swaiting for response

Description

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

  1. Restart the telegraf service
  2. Notice "nickname is already in use" error
  3. 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

Tech stack
go
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GoTelegraf plugin developmentTCP networkingTeamSpeak ServerQuery
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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.