Troubleshoot Telegraf Controller

Find the fix for a Telegraf Controller problem by its symptom. Symptoms appear in the server log output, in agent logs, or as errors in the web interface. For the log messages worth alerting on before they become problems, see Monitor Telegraf Controller.

Find your symptom

• address already in use at startup: another process holds one of the server’s ports. See Port already in use.
• Permission denied when running the binary, or macOS blocks the executable: the file is not executable, or the macOS quarantine attribute blocks it. See Permission denied.
• Browsers or agents cannot connect to a running server: a firewall blocks the server’s ports. See Ports are not reachable.
• Agent heartbeats return 401 Invalid token: the heartbeat service cannot validate tokens, often because its token cache cannot load. See Agent heartbeats return 401 Invalid token.
• Agents log x509: certificate signed by unknown authority: agents do not trust the server’s TLS certificate. See Agents do not trust the server certificate.
• database is locked, database or disk is full, or database disk image is malformed in the log: SQLite lock contention, disk exhaustion, or corruption. See Identify the failure type.
• The server cannot connect to PostgreSQL, or logs error performing TLS handshake: a connection string, network, or certificate trust problem. See PostgreSQL.
• License errors: a missing, expiring, or expired Telegraf Enterprise license. See Troubleshoot licensing.