influxdata/telegraf

TeamSpeak plugin "unexpected EOF" error

Closed

#15,738 建立於 2024年8月13日

在 GitHub 查看
 (2 留言) (0 反應) (1 負責人)Go (9,892 star) (4,161 fork)batch import
bughelp wantedsize/swaiting for response

描述

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.

貢獻者指南

技術棧
go
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GoTelegraf plugin developmentTCP networkingTeamSpeak ServerQuery
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
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.