Telegraf: [inputs.minecraft] Error in plugin: Server failed to mirror request challenge.

Created on 10 Sep 2020  路  8Comments  路  Source: influxdata/telegraf

Relevant telegraf.conf:

# minecraft input
[[inputs.minecraft]]
  server = "paper"
  port = "25575"
  password = ""
# prometheus export endpoint
[[outputs.prometheus_client]]
  listen = ":9012"
  metric_version = 2

System info:

Telegraf docker, latest (1.15.2)

Docker

Telegraf docker-compose:

---
version: "3"

networks:
  prom_network:
    external: true

services:
  telegraf:
    image: telegraf:latest
    restart: unless-stopped
    networks:
      - prom_network
    volumes:
      - "./data:/etc/telegraf/"

A paper minecraft server, docker-compose:

version: "3"

networks:
  minecraft:
  prom_network:
    external: true
services:
  paper:
    image: itzg/minecraft-server
    restart: unless-stopped
    networks:
      - minecraft
      - prom_network
    ports:
      - 25575:25575
    environment:
      EULA: "TRUE"
      MEMORY: "16G"
      TYPE: PAPER
      VERSION: 1.16.2
      USE_AIKAR_FLAGS: "true"
    volumes:
      - "./paper:/data"
      - /etc/timezone:/etc/timezone:ro

Steps to reproduce:

  1. Run minecraft server with docker-compose
  2. Run telegraf and attempt to connect to RCON with given configuration

Expected behavior:

Parsing of minecraft data via RCON

Actual behavior:

The following error, full logs included.

Telegraf

2020-09-10T03:06:55Z I! Starting Telegraf 1.15.2
2020-09-10T03:06:55Z D! [agent] Initializing plugins
2020-09-10T03:06:55Z D! [agent] Starting service inputs
2020-09-10T03:06:55Z E! [inputs.minecraft] Error in plugin: Server failed to mirror request challenge.
2020-09-10T03:06:55Z D! [agent] Stopping service inputs
2020-09-10T03:06:55Z D! [agent] Input channel closed
2020-09-10T03:06:55Z D! [agent] Stopped Successfully
2020-09-10T03:06:55Z E! [telegraf] Error running agent: input plugins recorded 1 errors

Additional info:

Minecraft logs, showing RCON client is getting connected to via Telegraf

[22:40:40 INFO]: Thread RCON Client /172.27.0.7 started
[22:40:50 INFO]: Thread RCON Client /172.27.0.7 started
[22:41:00 INFO]: Thread RCON Client /172.27.0.7 started
[22:41:06 INFO]: Thread RCON Client /172.27.0.7 shutting down
[22:41:06 INFO]: Thread RCON Client /172.27.0.7 shutting down
[22:41:06 INFO]: Thread RCON Client /172.27.0.7 shutting down

Relevant codebase here.

Willing to provide more information if necessary, thanks 馃槃

bug

All 8 comments

Looks like the client received a packet it didn't expect. Probably requires someone to do some debugging and figure out what packet was received and what to do with it. maybe @halfa or @jsoref ?

@ssoroka: why me?

I don't see why I was tagged either but I can take a look this week-end

@ZachMyers3 at the risk of hijacking the issue, I found the gathering of scoreboard metrics didn't help me for monitoring, so I developed a portable service to integrate health, player counts, and ping into telegraf/InfluxDB:

https://github.com/itzg/mc-monitor

Thanks @itzg, I got this up and running!

As for this existing issue, I'm happy to help see it through.

Let me know if any additional information is needed.

I think it's going to take someone debugging what's going on with the minecraft server communication protocol.

Sorry if I pinged anyone who hasn't worked on this plugin before; I believe your name came up in a git blame and I thought you might have some context.

Okay, if anything is needed from me I'm happy to provide whatever is necessary.

I have the same issue with similar configuration (minecraft server and telegraf on docker)

Was this page helpful?
0 / 5 - 0 ratings