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.
TeamSpeak plugin "unexpected EOF" error · influxdata/telegraf#15738 | Good First Issue